Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad9367fbcb2c14414b3262b54c5c1d6d63dcb87e23e80814ce8763e47ceeffc

Tx prefix hash: ca872cd142257e82150a9c93e91185663ed6c58c6d1cc24aaabee98455574bd3
Tx public key: e4ee2d15d71c39fcc86db729d5ddd6a93477366d267c339c78b89a16472b3482
Timestamp: 1721883619 Timestamp [UCT]: 2024-07-25 05:00:19 Age [y:d:h:m:s]: 00:211:22:31:03
Block: 1073161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151346 RingCT/type: yes/0
Extra: 01e4ee2d15d71c39fcc86db729d5ddd6a93477366d267c339c78b89a16472b3482021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60dd2d73a9c60ad0c60f1a61ac2c41b9f3638edc606b0e0f874e1ba930f516cb 0.600000000000 1545660 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": 1073171, "vin": [ { "gen": { "height": 1073161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60dd2d73a9c60ad0c60f1a61ac2c41b9f3638edc606b0e0f874e1ba930f516cb" } } ], "extra": [ 1, 228, 238, 45, 21, 215, 28, 57, 252, 200, 109, 183, 41, 213, 221, 214, 169, 52, 119, 54, 109, 38, 124, 51, 156, 120, 184, 154, 22, 71, 43, 52, 130, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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