Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ff99f6be7e2bbd5379eadbd85e41dde0138abe396aa21e5d7c1f14d59ea711

Tx prefix hash: 5e3622f67d7c727a5d8f27f35ab5e76e58f7ebc777aaa95e9d0c10833836af02
Tx public key: 245f266e405d619f3212717ccb7e98b8fb79aac3729cda8d747d9377fb58903e
Timestamp: 1718305977 Timestamp [UCT]: 2024-06-13 19:12:57 Age [y:d:h:m:s]: 00:274:10:52:23
Block: 1043514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196130 RingCT/type: yes/0
Extra: 01245f266e405d619f3212717ccb7e98b8fb79aac3729cda8d747d9377fb58903e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 698137f4f3ba8c46e4e69ca772d6d5ddd63a1fdc41c5e5ea3e8c63a0a252e19b 0.600000000000 1512667 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": 1043524, "vin": [ { "gen": { "height": 1043514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "698137f4f3ba8c46e4e69ca772d6d5ddd63a1fdc41c5e5ea3e8c63a0a252e19b" } } ], "extra": [ 1, 36, 95, 38, 110, 64, 93, 97, 159, 50, 18, 113, 124, 203, 126, 152, 184, 251, 121, 170, 195, 114, 156, 218, 141, 116, 125, 147, 119, 251, 88, 144, 62, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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