Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a4d5dd60130dcf15e4f36aed766deecf809c662484b2295abb4c23ebb8c2e6

Tx prefix hash: dc7e935903037936b1522107e7608e5a5c09ae77f17442e1483d4fa5946ab427
Tx public key: df11aa2f27011fbfde24f2e8a192ec9392c5672bb63077fd9831de1ca7e7b6f1
Timestamp: 1700032806 Timestamp [UCT]: 2023-11-15 07:20:06 Age [y:d:h:m:s]: 01:144:01:53:24
Block: 892012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364151 RingCT/type: yes/0
Extra: 01df11aa2f27011fbfde24f2e8a192ec9392c5672bb63077fd9831de1ca7e7b6f1021100000002faf35c9c000000000000000000

1 output(s) for total of 0.679820016000 dcy

stealth address amount amount idx
00: d33f47893688052370f8168605234dc7fa9680ef469ddcb240ca9af218dc080f 0.679820016000 1348071 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": 892022, "vin": [ { "gen": { "height": 892012 } } ], "vout": [ { "amount": 679820016, "target": { "key": "d33f47893688052370f8168605234dc7fa9680ef469ddcb240ca9af218dc080f" } } ], "extra": [ 1, 223, 17, 170, 47, 39, 1, 31, 191, 222, 36, 242, 232, 161, 146, 236, 147, 146, 197, 103, 43, 182, 48, 119, 253, 152, 49, 222, 28, 167, 231, 182, 241, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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