Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd6bc24969cf0b3c4ea2c82ee02af14139bf6eb02b2a31c23603b8381e14d13

Tx prefix hash: 05b8a663388db8bc5074330e5eec8cc8f53ad8ad5b75132c76195798e1c7b826
Tx public key: b26b086fc40f27e0243111fb6f744e094a42739affb0aa2b8ff38bef4cf0079e
Timestamp: 1726511796 Timestamp [UCT]: 2024-09-16 18:36:36 Age [y:d:h:m:s]: 00:239:10:03:02
Block: 1111539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170970 RingCT/type: yes/0
Extra: 01b26b086fc40f27e0243111fb6f744e094a42739affb0aa2b8ff38bef4cf0079e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 775574a187c1b4c8ac7f2ff23d19b1462e70097b5a4b94ba42ab528a366a9262 0.600000000000 1590536 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": 1111549, "vin": [ { "gen": { "height": 1111539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "775574a187c1b4c8ac7f2ff23d19b1462e70097b5a4b94ba42ab528a366a9262" } } ], "extra": [ 1, 178, 107, 8, 111, 196, 15, 39, 224, 36, 49, 17, 251, 111, 116, 78, 9, 74, 66, 115, 154, 255, 176, 170, 43, 143, 243, 139, 239, 76, 240, 7, 158, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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