Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39fe89654d8e96ce34c5b1e8e56d00a5dace4dd3635f3bd03ad4dfcb8332e1b3

Tx prefix hash: c5dc923187eed0c8d7e8dd0b0f0e290f1024f1396b9d2ea46b9534446331db79
Tx public key: d664bdde416ede5fcdec0ac7e8ab76aca2f4d9297f6c9cde89dfadacb2f516e3
Timestamp: 1733387493 Timestamp [UCT]: 2024-12-05 08:31:33 Age [y:d:h:m:s]: 00:101:16:07:21
Block: 1168444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72470 RingCT/type: yes/0
Extra: 01d664bdde416ede5fcdec0ac7e8ab76aca2f4d9297f6c9cde89dfadacb2f516e3021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0aa5dc40ca54b9d8927ab9f32a8bbebc1138b4e3534c6c8d8383de3a63a5d01 0.600000000000 1654153 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": 1168454, "vin": [ { "gen": { "height": 1168444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0aa5dc40ca54b9d8927ab9f32a8bbebc1138b4e3534c6c8d8383de3a63a5d01" } } ], "extra": [ 1, 214, 100, 189, 222, 65, 110, 222, 95, 205, 236, 10, 199, 232, 171, 118, 172, 162, 244, 217, 41, 127, 108, 156, 222, 137, 223, 173, 172, 178, 245, 22, 227, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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