Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36aeef457a4f7aefaedf6ca01400b05c536eeccd856653cdfd153000c0bc12cb

Tx prefix hash: 1a2f6c5d382553f5e87b37889ac862982790f81753fc254411da4ed5bb9aada5
Tx public key: a06cf67ddbc42beb51172ac2268ccd715932a5749a63f2d66d1b5bb1c9c1c78f
Timestamp: 1718823828 Timestamp [UCT]: 2024-06-19 19:03:48 Age [y:d:h:m:s]: 01:155:21:52:09
Block: 1047800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369997 RingCT/type: yes/0
Extra: 01a06cf67ddbc42beb51172ac2268ccd715932a5749a63f2d66d1b5bb1c9c1c78f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2fd34552197ce9aa9d8c5cc99a99e2b35c19199115fdf8077e945e3792847d7 0.600000000000 1517719 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": 1047810, "vin": [ { "gen": { "height": 1047800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2fd34552197ce9aa9d8c5cc99a99e2b35c19199115fdf8077e945e3792847d7" } } ], "extra": [ 1, 160, 108, 246, 125, 219, 196, 43, 235, 81, 23, 42, 194, 38, 140, 205, 113, 89, 50, 165, 116, 154, 99, 242, 214, 109, 27, 91, 177, 201, 193, 199, 143, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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