Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64dc41aa2bdaacb3e690012b4a5e4f19333ac2b4252dbdc2b70103c4d9d724b

Tx prefix hash: 536fd5e3cb193a740afc28ecf6e9f34ffaa47a5ea652907ab0e67f3d14a97202
Tx public key: c0ae23f9dfa33a5ff697ff7c44dd531cc09abbc343fb08d53e344a89f9c19302
Timestamp: 1725868071 Timestamp [UCT]: 2024-09-09 07:47:51 Age [y:d:h:m:s]: 01:058:13:06:53
Block: 1106213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300244 RingCT/type: yes/0
Extra: 01c0ae23f9dfa33a5ff697ff7c44dd531cc09abbc343fb08d53e344a89f9c1930202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8efbe4a2664508faabefd5d88d5849031b1d2fb7c43f1e931654005ea2cff5b8 0.600000000000 1583812 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": 1106223, "vin": [ { "gen": { "height": 1106213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8efbe4a2664508faabefd5d88d5849031b1d2fb7c43f1e931654005ea2cff5b8" } } ], "extra": [ 1, 192, 174, 35, 249, 223, 163, 58, 95, 246, 151, 255, 124, 68, 221, 83, 28, 192, 154, 187, 195, 67, 251, 8, 213, 62, 52, 74, 137, 249, 193, 147, 2, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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