Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc624d99b2469cc52255d40ea8a0efd37118636a9a5266b689530240ca71c29d

Tx prefix hash: 3afa5784d3684352f5eca3fba1503f5a5bdfd1e4d49851532cd3bc555931b9b2
Tx public key: e19c076d8b7c91bbb018490f7debed2e519837d36dc60a3e3e31c913663736dd
Timestamp: 1759381353 Timestamp [UCT]: 2025-10-02 05:02:33 Age [y:d:h:m:s]: 00:100:15:25:54
Block: 1380922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72085 RingCT/type: yes/0
Extra: 01e19c076d8b7c91bbb018490f7debed2e519837d36dc60a3e3e31c913663736dd021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc1bf7c92134b44e3fdd6ba0f0eb92b27e042005bb70691b8e71acdbcd97e27f 0.600000000000 1869033 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": 1380932, "vin": [ { "gen": { "height": 1380922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc1bf7c92134b44e3fdd6ba0f0eb92b27e042005bb70691b8e71acdbcd97e27f" } } ], "extra": [ 1, 225, 156, 7, 109, 139, 124, 145, 187, 176, 24, 73, 15, 125, 235, 237, 46, 81, 152, 55, 211, 109, 198, 10, 62, 62, 49, 201, 19, 102, 55, 54, 221, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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