Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed67ec0cffc9ae4c4a23ea2109f646cede8f40560620fd7f690773584866b93

Tx prefix hash: df3a5943a4f5f2f14561d0c0ba7842f139e643f05befc77dc9fc1c8ab71b34b5
Tx public key: b9477a6df1c4a5f83feee9829afbb523e291d76eb02189cf9ea991caa0988703
Timestamp: 1708286243 Timestamp [UCT]: 2024-02-18 19:57:23 Age [y:d:h:m:s]: 01:091:01:39:10
Block: 960447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326136 RingCT/type: yes/0
Extra: 01b9477a6df1c4a5f83feee9829afbb523e291d76eb02189cf9ea991caa09887030211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb54dd6ad24357766026d13dabfa120017d60e9d5683ebe6ed9facfd4890f08e 0.600000000000 1420012 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": 960457, "vin": [ { "gen": { "height": 960447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb54dd6ad24357766026d13dabfa120017d60e9d5683ebe6ed9facfd4890f08e" } } ], "extra": [ 1, 185, 71, 122, 109, 241, 196, 165, 248, 63, 238, 233, 130, 154, 251, 181, 35, 226, 145, 215, 110, 176, 33, 137, 207, 158, 169, 145, 202, 160, 152, 135, 3, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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