Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3b3d53f798ce302293912422fd9e49a372af2d49a96c5bbaada4b537e8b336e

Tx prefix hash: 4420b3f597fd95e423fc53876193ebe829bffbb0a1ba20f074e098b1a889e440
Tx public key: 93bb5784d19f92f9a11a65a7ff1c7fcfd8f381d980616e67e37c175f7ba1ffd2
Timestamp: 1725094297 Timestamp [UCT]: 2024-08-31 08:51:37 Age [y:d:h:m:s]: 00:241:09:01:45
Block: 1099790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172385 RingCT/type: yes/0
Extra: 0193bb5784d19f92f9a11a65a7ff1c7fcfd8f381d980616e67e37c175f7ba1ffd2021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b7e96d1d0b2cc25c815cc654677e0834834ccfdffaa729843237d4de508ff21 0.600000000000 1575759 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": 1099800, "vin": [ { "gen": { "height": 1099790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b7e96d1d0b2cc25c815cc654677e0834834ccfdffaa729843237d4de508ff21" } } ], "extra": [ 1, 147, 187, 87, 132, 209, 159, 146, 249, 161, 26, 101, 167, 255, 28, 127, 207, 216, 243, 129, 217, 128, 97, 110, 103, 227, 124, 23, 95, 123, 161, 255, 210, 2, 17, 0, 0, 0, 1, 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