Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: de93b8d822729128d92e139a82746392dfcf796f669302c40d23e66a98447330

Tx prefix hash: f2c9203a9022e359f88afe7299da76a565a0c7008e95fb13576cf43af5c0f0b9
Tx public key: f1707c0ae19ec2bb4e43802cde573d3c4ac8fc242bb5c77d792a4eb5571d17ce
Timestamp: 1718659965 Timestamp [UCT]: 2024-06-17 21:32:45 Age [y:d:h:m:s]: 00:271:12:08:18
Block: 1046446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194024 RingCT/type: yes/0
Extra: 01f1707c0ae19ec2bb4e43802cde573d3c4ac8fc242bb5c77d792a4eb5571d17ce0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d64b956fd92ef691b9f1a4751cea64ed65e4a49ddfd4b79e0378b4c3d3f563b 0.600000000000 1516259 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1046456, "vin": [ { "gen": { "height": 1046446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d64b956fd92ef691b9f1a4751cea64ed65e4a49ddfd4b79e0378b4c3d3f563b" } } ], "extra": [ 1, 241, 112, 124, 10, 225, 158, 194, 187, 78, 67, 128, 44, 222, 87, 61, 60, 74, 200, 252, 36, 43, 181, 199, 125, 121, 42, 78, 181, 87, 29, 23, 206, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8