Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d132f66b2ceae92e32952fedaaa1fe14bd0c965a99888a897278de7c73a9b0c8

Tx prefix hash: 3aca6ced14571935a7df06fe890fcf4de32e603b799ba5e4186850ae91389372
Tx public key: 3c8fac530d015ec9a01aa0d0ce818b8f2712ad6afb8ce3615261f5c7c0b88171
Timestamp: 1725239428 Timestamp [UCT]: 2024-09-02 01:10:28 Age [y:d:h:m:s]: 00:215:04:00:24
Block: 1100996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153616 RingCT/type: yes/0
Extra: 013c8fac530d015ec9a01aa0d0ce818b8f2712ad6afb8ce3615261f5c7c0b88171021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6632507ab4e9ad88303b87d94b064db2507c4b096b298816f96ce9a71f50ab2 0.600000000000 1576977 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": 1101006, "vin": [ { "gen": { "height": 1100996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6632507ab4e9ad88303b87d94b064db2507c4b096b298816f96ce9a71f50ab2" } } ], "extra": [ 1, 60, 143, 172, 83, 13, 1, 94, 201, 160, 26, 160, 208, 206, 129, 139, 143, 39, 18, 173, 106, 251, 140, 227, 97, 82, 97, 245, 199, 192, 184, 129, 113, 2, 17, 0, 0, 0, 7, 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