Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff0ade9c561db6248ab1af35da2e48a3c45e33283a32fcd3f7d4402fb96b920

Tx prefix hash: a7929edc05ec66ac24d8b2bb2680d22ac3d702da1530286d4d1829e325a0d205
Tx public key: 3aa308ef0db76dd446b30e507286d2e296aef3db03a3489b19afd1e99fb3519e
Timestamp: 1747745710 Timestamp [UCT]: 2025-05-20 12:55:10 Age [y:d:h:m:s]: 00:226:10:19:30
Block: 1287047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159590 RingCT/type: yes/0
Extra: 013aa308ef0db76dd446b30e507286d2e296aef3db03a3489b19afd1e99fb3519e0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a1123e0d0f34f12b32e188eda1b64a71248dd52ae725880049c9e9af8d6863 0.600000000000 1774514 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": 1287057, "vin": [ { "gen": { "height": 1287047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a1123e0d0f34f12b32e188eda1b64a71248dd52ae725880049c9e9af8d6863" } } ], "extra": [ 1, 58, 163, 8, 239, 13, 183, 109, 212, 70, 179, 14, 80, 114, 134, 210, 226, 150, 174, 243, 219, 3, 163, 72, 155, 25, 175, 209, 233, 159, 179, 81, 158, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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