Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77a2e52189773cb58d1722e89f77a7253165e1d291c30e11b6703617b33776d

Tx prefix hash: 7833d6cc7b05a10e09f68a3d18ef87cdb0f4621f0b63e8042366bb55f4d6c903
Tx public key: 7b94bddb0a5d85501188c9e0701903b07f5cfcfe59e59b03b3140b636b85b045
Timestamp: 1750656103 Timestamp [UCT]: 2025-06-23 05:21:43 Age [y:d:h:m:s]: 00:144:15:18:40
Block: 1310928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101265 RingCT/type: yes/0
Extra: 017b94bddb0a5d85501188c9e0701903b07f5cfcfe59e59b03b3140b636b85b045021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 980b98f096d6fa4cbb2557e0b312b51777d5ab7afc8d294b01416dcdca9d300f 0.600000000000 1798551 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": 1310938, "vin": [ { "gen": { "height": 1310928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "980b98f096d6fa4cbb2557e0b312b51777d5ab7afc8d294b01416dcdca9d300f" } } ], "extra": [ 1, 123, 148, 189, 219, 10, 93, 133, 80, 17, 136, 201, 224, 112, 25, 3, 176, 127, 92, 252, 254, 89, 229, 155, 3, 179, 20, 11, 99, 107, 133, 176, 69, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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