Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6285f9048ff247b6b3e815541c6e191587a0fb7bf2afe1abe9b9c8ac75431c8e

Tx prefix hash: 8149ca932668b76c3c00edf1b09097b5bf2cf29bf01bc99a2767cbc09fc20130
Tx public key: 751a8fb5c13ac3eec4cd42f0c94bdba7f6256efca063d29d669c7d8aa98ec27b
Timestamp: 1755295773 Timestamp [UCT]: 2025-08-15 22:09:33 Age [y:d:h:m:s]: 00:097:09:03:14
Block: 1347466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69317 RingCT/type: yes/0
Extra: 01751a8fb5c13ac3eec4cd42f0c94bdba7f6256efca063d29d669c7d8aa98ec27b0211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17034f736bd5f265996cff4cfda791b9e2daa7918f0d1640f15787410798509a 0.600000000000 1835383 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": 1347476, "vin": [ { "gen": { "height": 1347466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17034f736bd5f265996cff4cfda791b9e2daa7918f0d1640f15787410798509a" } } ], "extra": [ 1, 117, 26, 143, 181, 193, 58, 195, 238, 196, 205, 66, 240, 201, 75, 219, 167, 246, 37, 110, 252, 160, 99, 210, 157, 102, 156, 125, 138, 169, 142, 194, 123, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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