Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 860e58ad78eb93476ebfbb7add9a341b415af0b902be964c23aebd5791c0ce6a

Tx prefix hash: 93a325c7dadcd5469adc503553781e141ebcb8b88820f531f779907298f29775
Tx public key: 781203c9c76f0a1c1d12f8a9acbf36e3f0bd400d2742962f3b261b7ac53387de
Timestamp: 1733391170 Timestamp [UCT]: 2024-12-05 09:32:50 Age [y:d:h:m:s]: 00:193:22:33:26
Block: 1168479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138336 RingCT/type: yes/0
Extra: 01781203c9c76f0a1c1d12f8a9acbf36e3f0bd400d2742962f3b261b7ac53387de021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bddbbf5860862d2a787334298d4525345fbbaa3b9705e9f05ae5c08ce5808092 0.600000000000 1654188 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": 1168489, "vin": [ { "gen": { "height": 1168479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bddbbf5860862d2a787334298d4525345fbbaa3b9705e9f05ae5c08ce5808092" } } ], "extra": [ 1, 120, 18, 3, 201, 199, 111, 10, 28, 29, 18, 248, 169, 172, 191, 54, 227, 240, 189, 64, 13, 39, 66, 150, 47, 59, 38, 27, 122, 197, 51, 135, 222, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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