Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576ba2ee41808c0d2aa3b6bf419ef0674d43260f599f3cbe749a46f380881c9b

Tx prefix hash: 6e46ec166a103ee980c9cfcb7b2b2472b2a8a53865a1334b2f19400fc47ed2c1
Tx public key: 03c6d82f1ce775d5a20c427709837b68b82a180e3892e95dc3154944ab3e381e
Timestamp: 1734809784 Timestamp [UCT]: 2024-12-21 19:36:24 Age [y:d:h:m:s]: 00:093:00:59:02
Block: 1180250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66241 RingCT/type: yes/0
Extra: 0103c6d82f1ce775d5a20c427709837b68b82a180e3892e95dc3154944ab3e381e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dad9fea5f0ced06bf869a3b1a8be7ad9468e0bf9da8ec6a13bab0496ea631d3 0.600000000000 1666659 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": 1180260, "vin": [ { "gen": { "height": 1180250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dad9fea5f0ced06bf869a3b1a8be7ad9468e0bf9da8ec6a13bab0496ea631d3" } } ], "extra": [ 1, 3, 198, 216, 47, 28, 231, 117, 213, 162, 12, 66, 119, 9, 131, 123, 104, 184, 42, 24, 14, 56, 146, 233, 93, 195, 21, 73, 68, 171, 62, 56, 30, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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