Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5ccceaab0a514c832cb159109c9824c1635f39d4b33b596bfe667f46db3a656

Tx prefix hash: 69b32a93d1accb726196507932befa88b88d2cfb264f028180ac990d5406a5f8
Tx public key: 21c2ef46feae1688aef9436013e9e84289472548825eb59969b84abcc86836e5
Timestamp: 1737609992 Timestamp [UCT]: 2025-01-23 05:26:32 Age [y:d:h:m:s]: 00:053:06:00:21
Block: 1203357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37890 RingCT/type: yes/0
Extra: 0121c2ef46feae1688aef9436013e9e84289472548825eb59969b84abcc86836e50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64290e89ebb2f4045c5303c242a34a9e2e8a0169cbf76e3efc569c9160090d76 0.600000000000 1690034 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": 1203367, "vin": [ { "gen": { "height": 1203357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64290e89ebb2f4045c5303c242a34a9e2e8a0169cbf76e3efc569c9160090d76" } } ], "extra": [ 1, 33, 194, 239, 70, 254, 174, 22, 136, 174, 249, 67, 96, 19, 233, 232, 66, 137, 71, 37, 72, 130, 94, 181, 153, 105, 184, 74, 188, 200, 104, 54, 229, 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