Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9adfb127c0ad84125096e2d572f5f624adc6b41726e2cfd760b0ee0369b18128

Tx prefix hash: dd48db697f2ecaefebbd3e0a5497abc4ab0179b56299dc1eaa1a765813164889
Tx public key: 283ac4160e0619d07364c3edf91902eb695a1f0f52938af3f23580521426d64d
Timestamp: 1755028360 Timestamp [UCT]: 2025-08-12 19:52:40 Age [y:d:h:m:s]: 00:100:02:36:55
Block: 1345665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70867 RingCT/type: yes/0
Extra: 01283ac4160e0619d07364c3edf91902eb695a1f0f52938af3f23580521426d64d021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 606a3b250a0c674aaeb1d9ab782c1f5fdc1afebf65d23d5d5512d3079508e94f 0.600000000000 1833560 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": 1345675, "vin": [ { "gen": { "height": 1345665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606a3b250a0c674aaeb1d9ab782c1f5fdc1afebf65d23d5d5512d3079508e94f" } } ], "extra": [ 1, 40, 58, 196, 22, 14, 6, 25, 208, 115, 100, 195, 237, 249, 25, 2, 235, 105, 90, 31, 15, 82, 147, 138, 243, 242, 53, 128, 82, 20, 38, 214, 77, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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