Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb7a6e09a7d4c92549aed0f544c746120d5fce3ab4d5fe01e9ef61e8b1b185d8

Tx prefix hash: b89b08824ec3a0ae7472c48644ca0d7fd722b545c32446f58785e9bb192e0e5c
Tx public key: ac6f91fe89a384af54cfc4c7c63c0361c9a1dbfc3a1005c7d5ed5defbcccc59a
Timestamp: 1745743778 Timestamp [UCT]: 2025-04-27 08:49:38 Age [y:d:h:m:s]: 00:278:03:19:20
Block: 1270469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196417 RingCT/type: yes/0
Extra: 01ac6f91fe89a384af54cfc4c7c63c0361c9a1dbfc3a1005c7d5ed5defbcccc59a0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 353ac8f5b9a4376aa60e1cba3abd5dcba1f8bd77f6d5708cd75d657034271ad8 0.600000000000 1757712 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": 1270479, "vin": [ { "gen": { "height": 1270469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "353ac8f5b9a4376aa60e1cba3abd5dcba1f8bd77f6d5708cd75d657034271ad8" } } ], "extra": [ 1, 172, 111, 145, 254, 137, 163, 132, 175, 84, 207, 196, 199, 198, 60, 3, 97, 201, 161, 219, 252, 58, 16, 5, 199, 213, 237, 93, 239, 188, 204, 197, 154, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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