Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce727085eb1695b06866df144ae2da77cc504acd4b6f0cc13dbdd1af790dfcce

Tx prefix hash: 556b13dc0eeed591deec2c03606e815b504cf2c31bc7aed1fd5b8e9c14d084b3
Tx public key: 9aa56c23ef1a8fc882ac22fa8648d8756cbb28233860969f75c9037ea6b5b979
Timestamp: 1731184866 Timestamp [UCT]: 2024-11-09 20:41:06 Age [y:d:h:m:s]: 00:141:04:16:47
Block: 1150203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100716 RingCT/type: yes/0
Extra: 019aa56c23ef1a8fc882ac22fa8648d8756cbb28233860969f75c9037ea6b5b979021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40faf070d90917ad75e7989cd8a0283abd5d06d288118f075c21b9f37d4bcdfe 0.600000000000 1635444 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": 1150213, "vin": [ { "gen": { "height": 1150203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40faf070d90917ad75e7989cd8a0283abd5d06d288118f075c21b9f37d4bcdfe" } } ], "extra": [ 1, 154, 165, 108, 35, 239, 26, 143, 200, 130, 172, 34, 250, 134, 72, 216, 117, 108, 187, 40, 35, 56, 96, 150, 159, 117, 201, 3, 126, 166, 181, 185, 121, 2, 17, 0, 0, 0, 3, 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