Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf0a0c7fa107ce14d5250a53ede5d2ca9140d4dfc225646f1d199cfa56f4aaf3

Tx prefix hash: b9c856b861254a2b1409ca75c2d3b06faeaed22d38352f28cf9862f61a6bbf6f
Tx public key: bbe9ad3b31e0016eb912081802b1b5a2a67ac0c3b3302f1723e70d31214c1df2
Timestamp: 1648036117 Timestamp [UCT]: 2022-03-23 11:48:37 Age [y:d:h:m:s]: 02:228:00:50:22
Block: 464648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 682435 RingCT/type: yes/0
Extra: 01bbe9ad3b31e0016eb912081802b1b5a2a67ac0c3b3302f1723e70d31214c1df202110000000bd3fcec30000000000000000000

1 output(s) for total of 17.718565107000 dcy

stealth address amount amount idx
00: 1d1b5d7250a31310fd434cc99461b3cf82cef0394e4c07953ce2dc10d6e7dd50 17.718565107000 882575 of 0

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": 464658, "vin": [ { "gen": { "height": 464648 } } ], "vout": [ { "amount": 17718565107, "target": { "key": "1d1b5d7250a31310fd434cc99461b3cf82cef0394e4c07953ce2dc10d6e7dd50" } } ], "extra": [ 1, 187, 233, 173, 59, 49, 224, 1, 110, 185, 18, 8, 24, 2, 177, 181, 162, 166, 122, 192, 195, 179, 48, 47, 23, 35, 231, 13, 49, 33, 76, 29, 242, 2, 17, 0, 0, 0, 11, 211, 252, 236, 48, 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