Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4701026e5249c81d378219ad9ee30b032cffdd337480f26742ffa5cabf97b7a5

Tx prefix hash: 7909e4786268e79e8d1e5d6e971a2241ece4b45760de44f5e6c61e3801f0a590
Tx public key: 39e9fe904f41c9a431f4a42eede4fa4ba2a86ad0e0c1c6fa22be5b33d345a55a
Timestamp: 1749384280 Timestamp [UCT]: 2025-06-08 12:04:40 Age [y:d:h:m:s]: 00:155:13:10:13
Block: 1300618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108838 RingCT/type: yes/0
Extra: 0139e9fe904f41c9a431f4a42eede4fa4ba2a86ad0e0c1c6fa22be5b33d345a55a021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeb917bcd9f322057defee47388575ee12cff83970a966851bbe27c14f5c461c 0.600000000000 1788167 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": 1300628, "vin": [ { "gen": { "height": 1300618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeb917bcd9f322057defee47388575ee12cff83970a966851bbe27c14f5c461c" } } ], "extra": [ 1, 57, 233, 254, 144, 79, 65, 201, 164, 49, 244, 164, 46, 237, 228, 250, 75, 162, 168, 106, 208, 224, 193, 198, 250, 34, 190, 91, 51, 211, 69, 165, 90, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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