Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88a6a7f5261d499ffbd72a156d0bf7984e46a8bae76c2bd48594ed1e10df595d

Tx prefix hash: 5d782f86b1036a1d534ec68d76e865d7bc54d8cf585df303a84bbd1fcf9b290f
Tx public key: 1d3aa5edaae7e2ee7f6c8c223e51685f99d2c0f00140cdcfe90927e23f6e748f
Timestamp: 1763080627 Timestamp [UCT]: 2025-11-14 00:37:07 Age [y:d:h:m:s]: 00:057:18:06:55
Block: 1411589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41368 RingCT/type: yes/0
Extra: 011d3aa5edaae7e2ee7f6c8c223e51685f99d2c0f00140cdcfe90927e23f6e748f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24eaa9952fa97fedd645de64868d6581f5d44da4cfb151a651323cb81ef6ef85 0.600000000000 1900052 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": 1411599, "vin": [ { "gen": { "height": 1411589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24eaa9952fa97fedd645de64868d6581f5d44da4cfb151a651323cb81ef6ef85" } } ], "extra": [ 1, 29, 58, 165, 237, 170, 231, 226, 238, 127, 108, 140, 34, 62, 81, 104, 95, 153, 210, 192, 240, 1, 64, 205, 207, 233, 9, 39, 226, 63, 110, 116, 143, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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