Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd41316d054d53f023f73d04078c8b52546a6f4864f549f9c4741fa6db471a5

Tx prefix hash: 6d44459ef309e0b765b4fc6acee88e5bf150fc69399a0a905269ce4ca98de647
Tx public key: febec7a4e34f4aeaa6d04e57ff4aa9bd2c63e459d8372d71c780a73cee9c9bab
Timestamp: 1762444438 Timestamp [UCT]: 2025-11-06 15:53:58 Age [y:d:h:m:s]: 00:060:05:49:49
Block: 1406305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43166 RingCT/type: yes/0
Extra: 01febec7a4e34f4aeaa6d04e57ff4aa9bd2c63e459d8372d71c780a73cee9c9bab021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63790f435a31f2fbabe0d8a936fb979a64c50150bc0e6bf3ca3ed39401b17668 0.600000000000 1894688 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": 1406315, "vin": [ { "gen": { "height": 1406305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63790f435a31f2fbabe0d8a936fb979a64c50150bc0e6bf3ca3ed39401b17668" } } ], "extra": [ 1, 254, 190, 199, 164, 227, 79, 74, 234, 166, 208, 78, 87, 255, 74, 169, 189, 44, 99, 228, 89, 216, 55, 45, 113, 199, 128, 167, 60, 238, 156, 155, 171, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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