Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18f81f67aa3a1f40d6e2a85b20417b538a8e6ead3294d2ec310145239de7805

Tx prefix hash: 10562a8f776ecc6fb7ce78fc52efe9587a06e74e85eae4bbe128986deb2a2190
Tx public key: f31834cf59b9295fb20b4f71c52ae109cfe62d5a3551f61ab0af21c936f2c4a2
Timestamp: 1749646392 Timestamp [UCT]: 2025-06-11 12:53:12 Age [y:d:h:m:s]: 00:163:10:19:03
Block: 1302776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114492 RingCT/type: yes/0
Extra: 01f31834cf59b9295fb20b4f71c52ae109cfe62d5a3551f61ab0af21c936f2c4a2021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e172d741e7e8e9173b2fd13097547a99ad49895ec5a7a9fe2724463908a34dde 0.600000000000 1790349 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": 1302786, "vin": [ { "gen": { "height": 1302776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e172d741e7e8e9173b2fd13097547a99ad49895ec5a7a9fe2724463908a34dde" } } ], "extra": [ 1, 243, 24, 52, 207, 89, 185, 41, 95, 178, 11, 79, 113, 197, 42, 225, 9, 207, 230, 45, 90, 53, 81, 246, 26, 176, 175, 33, 201, 54, 242, 196, 162, 2, 17, 0, 0, 0, 2, 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