Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213dc0bf8278844268d298d567e18da375c150ae538d06a12eeb70bf59d2d994

Tx prefix hash: 6f020ea793d1b3f98b7a12894b4483cc8a1c5292bcaaeb0dca366681f58c8abd
Tx public key: 66f073d45208e5a0ef5f07c83d6bcb4c72bbf603ab5ab6bc31d25ed8cdaf1254
Timestamp: 1721991032 Timestamp [UCT]: 2024-07-26 10:50:32 Age [y:d:h:m:s]: 01:188:18:46:35
Block: 1074057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393341 RingCT/type: yes/0
Extra: 0166f073d45208e5a0ef5f07c83d6bcb4c72bbf603ab5ab6bc31d25ed8cdaf1254021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70c382a36673d79e68de3d6efa5b1856dcb5b92fe1580348f9a06beece3d37c2 0.600000000000 1546570 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": 1074067, "vin": [ { "gen": { "height": 1074057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70c382a36673d79e68de3d6efa5b1856dcb5b92fe1580348f9a06beece3d37c2" } } ], "extra": [ 1, 102, 240, 115, 212, 82, 8, 229, 160, 239, 95, 7, 200, 61, 107, 203, 76, 114, 187, 246, 3, 171, 90, 182, 188, 49, 210, 94, 216, 205, 175, 18, 84, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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