Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 217c5bcd32c0da889bffc06685bd07b1733e2983c9413fef8e7262a37c619eed

Tx prefix hash: f0b3d70a7671fa51c632ec64a4befcac5f8500c7ef6b90dc8173be4c3fb8e61a
Tx public key: 372476e1c02aa9c078aecd0701edb78c2eea9503db806034887bd14d2bd6b6ad
Timestamp: 1722383241 Timestamp [UCT]: 2024-07-30 23:47:21 Age [y:d:h:m:s]: 00:116:18:51:05
Block: 1077312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83557 RingCT/type: yes/0
Extra: 01372476e1c02aa9c078aecd0701edb78c2eea9503db806034887bd14d2bd6b6ad02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80fd1ddd847a4c2ffb97978627f0ce24e9b082d2671da5f4d471246b21ac94bb 0.600000000000 1549859 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": 1077322, "vin": [ { "gen": { "height": 1077312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80fd1ddd847a4c2ffb97978627f0ce24e9b082d2671da5f4d471246b21ac94bb" } } ], "extra": [ 1, 55, 36, 118, 225, 192, 42, 169, 192, 120, 174, 205, 7, 1, 237, 183, 140, 46, 234, 149, 3, 219, 128, 96, 52, 136, 123, 209, 77, 43, 214, 182, 173, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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