Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a1ba747f4d874634e6dc56f86cc7c18401fb963bdf6939c8c3d636eaa96257b

Tx prefix hash: 1da2c8a7e57a3545194175382b3195d64b9aa90061b9fb1d62c5766d9b7712a3
Tx public key: 7f6d032f255ec4b10d5e685f70005c9496d283c9db2e0318eebee5277ebf7d31
Timestamp: 1705118320 Timestamp [UCT]: 2024-01-13 03:58:40 Age [y:d:h:m:s]: 01:064:00:59:48
Block: 934160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306881 RingCT/type: yes/0
Extra: 017f6d032f255ec4b10d5e685f70005c9496d283c9db2e0318eebee5277ebf7d310211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4996034d1c328ee3d788f8b7f124cb1da87026bc62c5d351c515b9ebd02e6e64 0.600000000000 1392148 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": 934170, "vin": [ { "gen": { "height": 934160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4996034d1c328ee3d788f8b7f124cb1da87026bc62c5d351c515b9ebd02e6e64" } } ], "extra": [ 1, 127, 109, 3, 47, 37, 94, 196, 177, 13, 94, 104, 95, 112, 0, 92, 148, 150, 210, 131, 201, 219, 46, 3, 24, 238, 190, 229, 39, 126, 191, 125, 49, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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