Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bde43524f5fbf1a70c4ff129866b588f4452df121a955fb8a2f9f0908a9023e

Tx prefix hash: dc813d3b912ca4d40fb951f28bea42c531fecb77d91c2e995f9b387cf385659d
Tx public key: b35e9c53dea7708a0d8cddfde7fe7fd06091d988b378073ad3c3965b3c37eef4
Timestamp: 1762025925 Timestamp [UCT]: 2025-11-01 19:38:45 Age [y:d:h:m:s]: 00:009:03:43:53
Block: 1402851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6552 RingCT/type: yes/0
Extra: 01b35e9c53dea7708a0d8cddfde7fe7fd06091d988b378073ad3c3965b3c37eef40211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40c746ad5acdf42f15c4a107363df2778c005fc140b6b74f012a7ed72981d971 0.600000000000 1891176 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": 1402861, "vin": [ { "gen": { "height": 1402851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40c746ad5acdf42f15c4a107363df2778c005fc140b6b74f012a7ed72981d971" } } ], "extra": [ 1, 179, 94, 156, 83, 222, 167, 112, 138, 13, 140, 221, 253, 231, 254, 127, 208, 96, 145, 217, 136, 179, 120, 7, 58, 211, 195, 150, 91, 60, 55, 238, 244, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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