Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859d54ed72d7edf3607ba73e24d74b1423a1344fa427dc3d9137e0f05bd306b4

Tx prefix hash: bc58b3e78078ff589f53978bc2e49eef89948c0f5e714afef899b48239ecf6a8
Tx public key: 5be8739506c816044c417922c7cc4fff6d832497a0a24b3dbfc9104dc64acd0f
Timestamp: 1720537662 Timestamp [UCT]: 2024-07-09 15:07:42 Age [y:d:h:m:s]: 00:337:11:38:32
Block: 1062020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241140 RingCT/type: yes/0
Extra: 015be8739506c816044c417922c7cc4fff6d832497a0a24b3dbfc9104dc64acd0f021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 463d2f1e13ebcdbdeed483a36e26b01ea1027a8b71990a355370b083310f08a4 0.600000000000 1532521 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": 1062030, "vin": [ { "gen": { "height": 1062020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "463d2f1e13ebcdbdeed483a36e26b01ea1027a8b71990a355370b083310f08a4" } } ], "extra": [ 1, 91, 232, 115, 149, 6, 200, 22, 4, 76, 65, 121, 34, 199, 204, 79, 255, 109, 131, 36, 151, 160, 162, 75, 61, 191, 201, 16, 77, 198, 74, 205, 15, 2, 17, 0, 0, 0, 9, 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