Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca4447e0702672a9fc654f989d6046cad68a1af5e95068ec9c36bb33b19324d

Tx prefix hash: 817e362ff79f4fcc719ae9bb4cf9286e154dbee2f9e4a9005e73eab1f160b1fa
Tx public key: be7b8fa6d8c285ecc7c3eecdafed0bff3c760389c2d72c4b91ec4aebf53c1e45
Timestamp: 1708550001 Timestamp [UCT]: 2024-02-21 21:13:21 Age [y:d:h:m:s]: 01:032:23:50:23
Block: 962625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284603 RingCT/type: yes/0
Extra: 01be7b8fa6d8c285ecc7c3eecdafed0bff3c760389c2d72c4b91ec4aebf53c1e450211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4924846eef3fd906271c3310872b1014bf814be5b49b1d64bc290eccff849523 0.600000000000 1422282 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": 962635, "vin": [ { "gen": { "height": 962625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4924846eef3fd906271c3310872b1014bf814be5b49b1d64bc290eccff849523" } } ], "extra": [ 1, 190, 123, 143, 166, 216, 194, 133, 236, 199, 195, 238, 205, 175, 237, 11, 255, 60, 118, 3, 137, 194, 215, 44, 75, 145, 236, 74, 235, 245, 60, 30, 69, 2, 17, 0, 0, 0, 6, 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