Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ed267e57d35bf504ea037db6cf3ef825db745c79b8c9478d083a44b81af08c

Tx prefix hash: 049fc0b12695127eea1a090a5e670cadd101881e0a48865e9222b34b83fca952
Tx public key: 65857986bdd0bf8b77ceda19fddb912d47cef37ed896a4a872cfbaa7ece18740
Timestamp: 1754548715 Timestamp [UCT]: 2025-08-07 06:38:35 Age [y:d:h:m:s]: 00:094:17:48:00
Block: 1341947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66773 RingCT/type: yes/0
Extra: 0165857986bdd0bf8b77ceda19fddb912d47cef37ed896a4a872cfbaa7ece1874002110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e0ee3aac05a57260d4f1c933cb18244c814f0dc21aa72e8efc6a9f2d702ca8c 0.600000000000 1829776 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": 1341957, "vin": [ { "gen": { "height": 1341947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e0ee3aac05a57260d4f1c933cb18244c814f0dc21aa72e8efc6a9f2d702ca8c" } } ], "extra": [ 1, 101, 133, 121, 134, 189, 208, 191, 139, 119, 206, 218, 25, 253, 219, 145, 45, 71, 206, 243, 126, 216, 150, 164, 168, 114, 207, 186, 167, 236, 225, 135, 64, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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