Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cceb069b60195cdcf5c201915175660a3e95ea0f5ad33af4c881d01bee083da1

Tx prefix hash: db242896d6271b50561fd812757ed74096bc3bd535ccee1de6aa369605bc7469
Tx public key: bd600d36ea09d42d890fab0f0d2f4e81f4e707b56cb5ee8e35b18cb237d7e903
Timestamp: 1701820664 Timestamp [UCT]: 2023-12-05 23:57:44 Age [y:d:h:m:s]: 01:157:10:47:43
Block: 906838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373702 RingCT/type: yes/0
Extra: 01bd600d36ea09d42d890fab0f0d2f4e81f4e707b56cb5ee8e35b18cb237d7e903021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.607112582000 dcy

stealth address amount amount idx
00: e0f5c0981f1914c94c1bb20d1a4454b2e48c91a04e24ee1837d8c3c7cfbe06f5 0.607112582000 1363797 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": 906848, "vin": [ { "gen": { "height": 906838 } } ], "vout": [ { "amount": 607112582, "target": { "key": "e0f5c0981f1914c94c1bb20d1a4454b2e48c91a04e24ee1837d8c3c7cfbe06f5" } } ], "extra": [ 1, 189, 96, 13, 54, 234, 9, 212, 45, 137, 15, 171, 15, 13, 47, 78, 129, 244, 231, 7, 181, 108, 181, 238, 142, 53, 177, 140, 178, 55, 215, 233, 3, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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