Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c46a1d77c8fdb13dd9b4cec988fcd8e3df0ec45410ede7a5662e88f35482e017

Tx prefix hash: 42fb44e1f7bf7073d0df8a4a0394edce3187c7f73c60cf29088cbb16d287333b
Tx public key: 63ad2dbbfcde748e7724b3414702d3de9c0c624bb894525fb52061ee4e90130d
Timestamp: 1764833634 Timestamp [UCT]: 2025-12-04 07:33:54 Age [y:d:h:m:s]: 00:035:06:39:45
Block: 1426121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25260 RingCT/type: yes/0
Extra: 0163ad2dbbfcde748e7724b3414702d3de9c0c624bb894525fb52061ee4e90130d021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 916b4d3cd04d5d82183c3babad5889b64877245198276f4e2f61b13dd901b5a2 0.600000000000 1914804 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": 1426131, "vin": [ { "gen": { "height": 1426121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "916b4d3cd04d5d82183c3babad5889b64877245198276f4e2f61b13dd901b5a2" } } ], "extra": [ 1, 99, 173, 45, 187, 252, 222, 116, 142, 119, 36, 179, 65, 71, 2, 211, 222, 156, 12, 98, 75, 184, 148, 82, 95, 181, 32, 97, 238, 78, 144, 19, 13, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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