Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e877474f7ba1a3e6b27278ed2a6a1e92c9d24058d7c7801f76856e808d0f53d7

Tx prefix hash: b855ee94dba05bc5d1c3495dd5779e508954dc78218f986b4678bb56ce276383
Tx public key: ed417fe100a052f9ea69bd6741983600c3e1abb35c22ba6fe1f8df9d2eed96d3
Timestamp: 1764626241 Timestamp [UCT]: 2025-12-01 21:57:21 Age [y:d:h:m:s]: 00:020:12:48:03
Block: 1424402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14695 RingCT/type: yes/0
Extra: 01ed417fe100a052f9ea69bd6741983600c3e1abb35c22ba6fe1f8df9d2eed96d302110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe1540d8fc42a2ddb19d94ad5a175c3ee1df33f1b856585f2c9ea1c985d726c 0.600000000000 1913033 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": 1424412, "vin": [ { "gen": { "height": 1424402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe1540d8fc42a2ddb19d94ad5a175c3ee1df33f1b856585f2c9ea1c985d726c" } } ], "extra": [ 1, 237, 65, 127, 225, 0, 160, 82, 249, 234, 105, 189, 103, 65, 152, 54, 0, 195, 225, 171, 179, 92, 34, 186, 111, 225, 248, 223, 157, 46, 237, 150, 211, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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