Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1618144ff4ac6d1a193d934fbc5643bbe2f2140ae432ccc265c9bf8cfd2db0

Tx prefix hash: 53f386c9ab682e11ff4e69a34a6362c4ea2198d5d7d58ccc12c7546d88977f85
Tx public key: 82d4598f31d966402cb0986a09c2544d286cfbf8bb6dfb5b8e582286b11e3bbe
Timestamp: 1759048813 Timestamp [UCT]: 2025-09-28 08:40:13 Age [y:d:h:m:s]: 00:009:14:06:20
Block: 1378171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6856 RingCT/type: yes/0
Extra: 0182d4598f31d966402cb0986a09c2544d286cfbf8bb6dfb5b8e582286b11e3bbe021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e62886624c5ef5dc154937b33854aeda1dd303d214ab0b3558064a8e2749230f 0.600000000000 1866266 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": 1378181, "vin": [ { "gen": { "height": 1378171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e62886624c5ef5dc154937b33854aeda1dd303d214ab0b3558064a8e2749230f" } } ], "extra": [ 1, 130, 212, 89, 143, 49, 217, 102, 64, 44, 176, 152, 106, 9, 194, 84, 77, 40, 108, 251, 248, 187, 109, 251, 91, 142, 88, 34, 134, 177, 30, 59, 190, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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