Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03a3b3825bbd678e7a197c0c1f959c82bec75028b994a742bff5c7986419613

Tx prefix hash: 92baac13f4e0f703b772c6df97333bf6efd407af69997baa57d5fc7bcb8b783c
Tx public key: eafd35924aee59b43e6e95abef3ea888f9fcdcd522aef724724fbe06ea4f09e9
Timestamp: 1722544230 Timestamp [UCT]: 2024-08-01 20:30:30 Age [y:d:h:m:s]: 00:301:18:33:17
Block: 1078642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215632 RingCT/type: yes/0
Extra: 01eafd35924aee59b43e6e95abef3ea888f9fcdcd522aef724724fbe06ea4f09e9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 419bf3fe0df85a8151177e2b99a1de68485b6c525e2bc87497c1d2d10169a83c 0.600000000000 1551259 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": 1078652, "vin": [ { "gen": { "height": 1078642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "419bf3fe0df85a8151177e2b99a1de68485b6c525e2bc87497c1d2d10169a83c" } } ], "extra": [ 1, 234, 253, 53, 146, 74, 238, 89, 180, 62, 110, 149, 171, 239, 62, 168, 136, 249, 252, 220, 213, 34, 174, 247, 36, 114, 79, 190, 6, 234, 79, 9, 233, 2, 17, 0, 0, 0, 2, 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