Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72b728cdcdda32fd5c1e36c0815d0b3f651dc2ce8b5abf294622efdfd1471c5

Tx prefix hash: 529fcec821329727be866d4b81b45bd37e509faeeff365a2db8e1f0b62efee42
Tx public key: a5cabf782adb89cdae055c5867d1a37594afe412b694ba7aa7c7ffa5f0f99787
Timestamp: 1763263651 Timestamp [UCT]: 2025-11-16 03:27:31 Age [y:d:h:m:s]: 00:012:05:59:42
Block: 1413100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8780 RingCT/type: yes/0
Extra: 01a5cabf782adb89cdae055c5867d1a37594afe412b694ba7aa7c7ffa5f0f9978702110000000317b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 261af423972570cbe7f8ddfc53f2de9f21a804fd5265bcabb26d13c41e4221f1 0.600000000000 1901577 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": 1413110, "vin": [ { "gen": { "height": 1413100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "261af423972570cbe7f8ddfc53f2de9f21a804fd5265bcabb26d13c41e4221f1" } } ], "extra": [ 1, 165, 202, 191, 120, 42, 219, 137, 205, 174, 5, 92, 88, 103, 209, 163, 117, 148, 175, 228, 18, 182, 148, 186, 122, 167, 199, 255, 165, 240, 249, 151, 135, 2, 17, 0, 0, 0, 3, 23, 177, 145, 50, 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