Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c548e050e5ae99ac7563aea6e741e445ea29af66212c1ea44c37f3251ee98c71

Tx prefix hash: 3da61934434b7c45a8c2d953a3645d76347287eb8a2d0a5de57eef9050420077
Tx public key: 87b1c616d8e5db1ec86ba0a39b59ffdd0b02cb9f6e0f7ede9cf4a68e24f9313d
Timestamp: 1724773913 Timestamp [UCT]: 2024-08-27 15:51:53 Age [y:d:h:m:s]: 00:088:16:23:46
Block: 1097123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63436 RingCT/type: yes/0
Extra: 0187b1c616d8e5db1ec86ba0a39b59ffdd0b02cb9f6e0f7ede9cf4a68e24f9313d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2cec6153cdda5bd0b49d74aba61cd830fd363dff4b3ea6511e8b9aa57f17abf 0.600000000000 1572430 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": 1097133, "vin": [ { "gen": { "height": 1097123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2cec6153cdda5bd0b49d74aba61cd830fd363dff4b3ea6511e8b9aa57f17abf" } } ], "extra": [ 1, 135, 177, 198, 22, 216, 229, 219, 30, 200, 107, 160, 163, 155, 89, 255, 221, 11, 2, 203, 159, 110, 15, 126, 222, 156, 244, 166, 142, 36, 249, 49, 61, 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