Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e2c8ebc87fc61f058d826f184819a0ff324e436b685acab1a23a840f7c709e

Tx prefix hash: 62dc87066c1d98c6aed0868d9048edc9d3bac53768b86af64391a68c6dcb5f00
Tx public key: 6ccd57217b8f34ee8a62b8ccaac3041047bdc56914d8d6da42921d3de1ae31e2
Timestamp: 1745706352 Timestamp [UCT]: 2025-04-26 22:25:52 Age [y:d:h:m:s]: 00:016:02:43:12
Block: 1270164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11517 RingCT/type: yes/0
Extra: 016ccd57217b8f34ee8a62b8ccaac3041047bdc56914d8d6da42921d3de1ae31e2021100000001f7011ad5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cee770556f5479b79c9dae0a58d628a182ebcbba75072e0e263df2e07a2726b 0.600000000000 1757405 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": 1270174, "vin": [ { "gen": { "height": 1270164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cee770556f5479b79c9dae0a58d628a182ebcbba75072e0e263df2e07a2726b" } } ], "extra": [ 1, 108, 205, 87, 33, 123, 143, 52, 238, 138, 98, 184, 204, 170, 195, 4, 16, 71, 189, 197, 105, 20, 216, 214, 218, 66, 146, 29, 61, 225, 174, 49, 226, 2, 17, 0, 0, 0, 1, 247, 1, 26, 213, 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