Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29a156fd2ea9831eee6da8366d0923df9ed131f6a61d5f4032e8e2986fca4d42

Tx prefix hash: 783258eb8965de1094e3946075db6e6513f9f67f28504f31fb2484f9c5f982f0
Tx public key: 01f8f9ea12e53309aea9094b55d60dfcb8d69202b3c2cfcd84c2fb7a88a9ca4f
Timestamp: 1717098660 Timestamp [UCT]: 2024-05-30 19:51:00 Age [y:d:h:m:s]: 01:163:02:10:53
Block: 1033503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375151 RingCT/type: yes/0
Extra: 0101f8f9ea12e53309aea9094b55d60dfcb8d69202b3c2cfcd84c2fb7a88a9ca4f02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f5b21135df0e5863b19b7d5160c59494223a85c6112c691a9881b32c075b205 0.600000000000 1501972 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": 1033513, "vin": [ { "gen": { "height": 1033503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f5b21135df0e5863b19b7d5160c59494223a85c6112c691a9881b32c075b205" } } ], "extra": [ 1, 1, 248, 249, 234, 18, 229, 51, 9, 174, 169, 9, 75, 85, 214, 13, 252, 184, 214, 146, 2, 179, 194, 207, 205, 132, 194, 251, 122, 136, 169, 202, 79, 2, 17, 0, 0, 0, 8, 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