Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a609ac535b772bfd676fe3757f145f4cd645500a6ac9ac9b560274bd8749faa3

Tx prefix hash: 98af913f12764bc31486f3d91b51f2d3567c9a89d7fdb53c4e7dba699024c8c9
Tx public key: 1512d6432117b397174dd2a10e4c0d6d3a4a8857f110fd14631d36ad7dc3ad82
Timestamp: 1741420289 Timestamp [UCT]: 2025-03-08 07:51:29 Age [y:d:h:m:s]: 00:331:06:38:17
Block: 1234684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234426 RingCT/type: yes/0
Extra: 011512d6432117b397174dd2a10e4c0d6d3a4a8857f110fd14631d36ad7dc3ad8202110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d346c89d70f5d916fe656c8a1472cb8606c8dbf3b85c9436e5311203e08ee8e 0.600000000000 1721617 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": 1234694, "vin": [ { "gen": { "height": 1234684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d346c89d70f5d916fe656c8a1472cb8606c8dbf3b85c9436e5311203e08ee8e" } } ], "extra": [ 1, 21, 18, 214, 67, 33, 23, 179, 151, 23, 77, 210, 161, 14, 76, 13, 109, 58, 74, 136, 87, 241, 16, 253, 20, 99, 29, 54, 173, 125, 195, 173, 130, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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