Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad0db1a59e93305963c65c9b08552672f14c9ba633e998580f83030df5dd845

Tx prefix hash: 2dc22ebb4a6958037c074f315a145ddb54a2a497b20f9cfe1a6512c3ea2c925f
Tx public key: d2f19ad2692fd959968162e63993415c86c7ae5fe1dbe3beb2959fa4979f127f
Timestamp: 1732608182 Timestamp [UCT]: 2024-11-26 08:03:02 Age [y:d:h:m:s]: 00:123:03:18:00
Block: 1161986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87816 RingCT/type: yes/0
Extra: 01d2f19ad2692fd959968162e63993415c86c7ae5fe1dbe3beb2959fa4979f127f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e3a09ac36e955781230a8852c954f15d4e602ee945328549e4206cb226a6cd6 0.600000000000 1647641 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": 1161996, "vin": [ { "gen": { "height": 1161986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e3a09ac36e955781230a8852c954f15d4e602ee945328549e4206cb226a6cd6" } } ], "extra": [ 1, 210, 241, 154, 210, 105, 47, 217, 89, 150, 129, 98, 230, 57, 147, 65, 92, 134, 199, 174, 95, 225, 219, 227, 190, 178, 149, 159, 164, 151, 159, 18, 127, 2, 17, 0, 0, 0, 1, 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