Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2514a4cb569d4d3c31d421749091e485da497241b42bd49cc4ee3961790ac899

Tx prefix hash: 7cbeb17d98e5c7bf5349e551a6bc14c07d4bdd07edb286de36be7e5717577ca6
Tx public key: 12ee11435ea2c1336693f690a0e36bb64ffe432c2c11e98e51e8bbf24da3dac1
Timestamp: 1723357241 Timestamp [UCT]: 2024-08-11 06:20:41 Age [y:d:h:m:s]: 00:290:22:36:03
Block: 1085387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207871 RingCT/type: yes/0
Extra: 0112ee11435ea2c1336693f690a0e36bb64ffe432c2c11e98e51e8bbf24da3dac1021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3197667c3fc3b8f559064f1368633d1a53d8e943f0e6af837e5f2b2f22b8bf3b 0.600000000000 1559960 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": 1085397, "vin": [ { "gen": { "height": 1085387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3197667c3fc3b8f559064f1368633d1a53d8e943f0e6af837e5f2b2f22b8bf3b" } } ], "extra": [ 1, 18, 238, 17, 67, 94, 162, 193, 51, 102, 147, 246, 144, 160, 227, 107, 182, 79, 254, 67, 44, 44, 17, 233, 142, 81, 232, 187, 242, 77, 163, 218, 193, 2, 17, 0, 0, 0, 8, 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