Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e95772b7cd7aafe7b6e0a3c26a5cf1959185369c9329a56a3abb04ffac76b04

Tx prefix hash: 655df50f0d40d944b869b783673ac066d2d65a6f1c8856238bc3a57cc6fd3cfb
Tx public key: 071d01247e40e9e1c4a42a25bb2322c11be6ce1c26282aef2e4854998226e99d
Timestamp: 1754577944 Timestamp [UCT]: 2025-08-07 14:45:44 Age [y:d:h:m:s]: 00:104:16:16:20
Block: 1342187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73883 RingCT/type: yes/0
Extra: 01071d01247e40e9e1c4a42a25bb2322c11be6ce1c26282aef2e4854998226e99d021100000009b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 653dc435dbbe03a20212ffe7935520ce09f482be699e8e8452f3720b67fd8e77 0.600000000000 1830018 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": 1342197, "vin": [ { "gen": { "height": 1342187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "653dc435dbbe03a20212ffe7935520ce09f482be699e8e8452f3720b67fd8e77" } } ], "extra": [ 1, 7, 29, 1, 36, 126, 64, 233, 225, 196, 164, 42, 37, 187, 35, 34, 193, 27, 230, 206, 28, 38, 40, 42, 239, 46, 72, 84, 153, 130, 38, 233, 157, 2, 17, 0, 0, 0, 9, 178, 247, 132, 196, 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