Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1a6e4731e732655c71ca2d7a54ec1276111845988c35d6db5159fd959a96612

Tx prefix hash: 606d2c33834bc0d43a04299750e7c8c7da6c5b63a0486a48e25aa1e78227a25f
Tx public key: 48c09fc3d31bf1fb54ac543da28c2dd946f6c3d8c736ede4119d0ad0bbf0afa6
Timestamp: 1750993713 Timestamp [UCT]: 2025-06-27 03:08:33 Age [y:d:h:m:s]: 00:140:13:46:29
Block: 1313591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98483 RingCT/type: yes/0
Extra: 0148c09fc3d31bf1fb54ac543da28c2dd946f6c3d8c736ede4119d0ad0bbf0afa60211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e280214a605ab736047486d99d32d23ff0650809f12ba2f8ab017485675dfc7c 0.600000000000 1801232 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": 1313601, "vin": [ { "gen": { "height": 1313591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e280214a605ab736047486d99d32d23ff0650809f12ba2f8ab017485675dfc7c" } } ], "extra": [ 1, 72, 192, 159, 195, 211, 27, 241, 251, 84, 172, 84, 61, 162, 140, 45, 217, 70, 246, 195, 216, 199, 54, 237, 228, 17, 157, 10, 208, 187, 240, 175, 166, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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