Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3cb22eff4290b14f2f19e194bf82828eee20cc6524bc346ca542d11d193ab4c

Tx prefix hash: 846ce8d2f18c3199999629d97f0f9a5ab8bbb562ed0f0552205f327e5e3d1c91
Tx public key: 7d8188669916c39a639da0e8a6b679ed002dd368bf2fd272fadea2d662d0a280
Timestamp: 1738388977 Timestamp [UCT]: 2025-02-01 05:49:37 Age [y:d:h:m:s]: 00:292:19:50:00
Block: 1209584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207034 RingCT/type: yes/0
Extra: 017d8188669916c39a639da0e8a6b679ed002dd368bf2fd272fadea2d662d0a280021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78aa440cd22a09c7b0b0d1aa4653feb3d7343d69545ae8b8a5311bc2552ced1f 0.600000000000 1696329 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": 1209594, "vin": [ { "gen": { "height": 1209584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78aa440cd22a09c7b0b0d1aa4653feb3d7343d69545ae8b8a5311bc2552ced1f" } } ], "extra": [ 1, 125, 129, 136, 102, 153, 22, 195, 154, 99, 157, 160, 232, 166, 182, 121, 237, 0, 45, 211, 104, 191, 47, 210, 114, 250, 222, 162, 214, 98, 208, 162, 128, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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