Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d5ba491f601b57f2e7eecdf66fafdabc8eb373009acde592fbf1f3915c5d9c

Tx prefix hash: a38b603b08d60901c018861528747864c8af7f51b00b589b9e297484d011df5a
Tx public key: e470e61a927664c2cf0472dd00bae734def9c52ce77b2bcab4bcadf8cdcae494
Timestamp: 1649456162 Timestamp [UCT]: 2022-04-08 22:16:02 Age [y:d:h:m:s]: 03:036:08:45:23
Block: 476122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806458 RingCT/type: yes/0
Extra: 01e470e61a927664c2cf0472dd00bae734def9c52ce77b2bcab4bcadf8cdcae49402110000000306faf294000000000000000000

1 output(s) for total of 16.233434269000 dcy

stealth address amount amount idx
00: d2998ae2584e7fd976e9cf1f81309866e3a81cd6cbae15ad3f3fb0b80e4332be 16.233434269000 896509 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": 476132, "vin": [ { "gen": { "height": 476122 } } ], "vout": [ { "amount": 16233434269, "target": { "key": "d2998ae2584e7fd976e9cf1f81309866e3a81cd6cbae15ad3f3fb0b80e4332be" } } ], "extra": [ 1, 228, 112, 230, 26, 146, 118, 100, 194, 207, 4, 114, 221, 0, 186, 231, 52, 222, 249, 197, 44, 231, 123, 43, 202, 180, 188, 173, 248, 205, 202, 228, 148, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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