Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c5ba35dc633b88beb0f74cfa9f45282049d5afea569abcbd75d3cbde12ea17

Tx prefix hash: 30649619be258074ee41645eee9c23416ee5969f2ad715894f84f09c0a9ec141
Tx public key: 2399598d2c3b1a08c2ccf12b85142d4a357ae9c6febb697e6527e312edb7208a
Timestamp: 1707217729 Timestamp [UCT]: 2024-02-06 11:08:49 Age [y:d:h:m:s]: 01:130:09:40:33
Block: 951580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354196 RingCT/type: yes/0
Extra: 012399598d2c3b1a08c2ccf12b85142d4a357ae9c6febb697e6527e312edb7208a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d2a054ae1ae20261dbbed9306a41ad917b753a62f4c4bad81a2977b2dbad416 0.600000000000 1410362 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": 951590, "vin": [ { "gen": { "height": 951580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d2a054ae1ae20261dbbed9306a41ad917b753a62f4c4bad81a2977b2dbad416" } } ], "extra": [ 1, 35, 153, 89, 141, 44, 59, 26, 8, 194, 204, 241, 43, 133, 20, 45, 74, 53, 122, 233, 198, 254, 187, 105, 126, 101, 39, 227, 18, 237, 183, 32, 138, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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