Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 945b7c20079543a644a3b91367a5642370cf0cebd85a01b91ead70dcd8445fdc

Tx prefix hash: eb7f086ed1ceed323b44da9a8206d8aae14507973cdff7cd257bcc8b4bf1797e
Tx public key: 16750fda0219146cdd7a88b49f91e8d7d603db86474b57f308ef23f89f3d966c
Timestamp: 1725365820 Timestamp [UCT]: 2024-09-03 12:17:00 Age [y:d:h:m:s]: 00:081:19:47:13
Block: 1102041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58514 RingCT/type: yes/0
Extra: 0116750fda0219146cdd7a88b49f91e8d7d603db86474b57f308ef23f89f3d966c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3804a1eecbc73f4a60c6f8067abc16c29fc008e16d8f5d7a8b650f0ecd44d0dd 0.600000000000 1578324 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": 1102051, "vin": [ { "gen": { "height": 1102041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3804a1eecbc73f4a60c6f8067abc16c29fc008e16d8f5d7a8b650f0ecd44d0dd" } } ], "extra": [ 1, 22, 117, 15, 218, 2, 25, 20, 108, 221, 122, 136, 180, 159, 145, 232, 215, 214, 3, 219, 134, 71, 75, 87, 243, 8, 239, 35, 248, 159, 61, 150, 108, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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