Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0541ec58d8c17a1882ffeb9dac2f7115382687d0750a4c573fa8f0adb1bfaa12

Tx prefix hash: 5f80cff082fc0a18cc1e79a8aea40f468e6f82831e432724d5567c4b10ad9071
Tx public key: de2d10b3c1a88bd82c18c95105d4e08c5cda57ab568cd8e4226033d53220d6c0
Timestamp: 1759873112 Timestamp [UCT]: 2025-10-07 21:38:32 Age [y:d:h:m:s]: 00:034:03:34:55
Block: 1385000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24453 RingCT/type: yes/0
Extra: 01de2d10b3c1a88bd82c18c95105d4e08c5cda57ab568cd8e4226033d53220d6c0021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e44be239af5d10a94a7590f9ccd5d0a8cc0f8ed96d0427695974a87c3b88306 0.600000000000 1873157 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": 1385010, "vin": [ { "gen": { "height": 1385000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e44be239af5d10a94a7590f9ccd5d0a8cc0f8ed96d0427695974a87c3b88306" } } ], "extra": [ 1, 222, 45, 16, 179, 193, 168, 139, 216, 44, 24, 201, 81, 5, 212, 224, 140, 92, 218, 87, 171, 86, 140, 216, 228, 34, 96, 51, 213, 50, 32, 214, 192, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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