Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bac4b3bd20bca4cb28f21b7c3f7a6031b6a6adbe1606805d9a98763065c5ab79

Tx prefix hash: 91fa72c1ab381648fff9c0b6c1383a249ae650c92716652370af238fb21c06b9
Tx public key: 461ad4cc41f873569282ece49a6ab0e42b3bacdfd0a91f95934468fdf7b5a277
Timestamp: 1741665964 Timestamp [UCT]: 2025-03-11 04:06:04 Age [y:d:h:m:s]: 00:255:19:55:48
Block: 1236720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180574 RingCT/type: yes/0
Extra: 01461ad4cc41f873569282ece49a6ab0e42b3bacdfd0a91f95934468fdf7b5a277021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25a8b078698b250a1d8f344b1f44def5aefb852ee798bc28a977a4dc300b5562 0.600000000000 1723671 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": 1236730, "vin": [ { "gen": { "height": 1236720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a8b078698b250a1d8f344b1f44def5aefb852ee798bc28a977a4dc300b5562" } } ], "extra": [ 1, 70, 26, 212, 204, 65, 248, 115, 86, 146, 130, 236, 228, 154, 106, 176, 228, 43, 59, 172, 223, 208, 169, 31, 149, 147, 68, 104, 253, 247, 181, 162, 119, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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