Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a74c30d51d8e9b4e82dccda53262489235217edf008c019173fe3b4aad4f2c1

Tx prefix hash: 0f9f2827a9386481432c8ebcad18da868dbed79c863a6c4cf8bc97f88779d130
Tx public key: 439a2da5544d5ee7d65f7c3ee2efa9d60902d3ee9bac86a72dfefa76936e9a6a
Timestamp: 1726085613 Timestamp [UCT]: 2024-09-11 20:13:33 Age [y:d:h:m:s]: 00:184:03:24:46
Block: 1108002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131451 RingCT/type: yes/0
Extra: 01439a2da5544d5ee7d65f7c3ee2efa9d60902d3ee9bac86a72dfefa76936e9a6a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8592f0aa5dd5fc4aaa558ecfd47c7fc2dec63115607f65d9b62e59a212520341 0.600000000000 1585745 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": 1108012, "vin": [ { "gen": { "height": 1108002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8592f0aa5dd5fc4aaa558ecfd47c7fc2dec63115607f65d9b62e59a212520341" } } ], "extra": [ 1, 67, 154, 45, 165, 84, 77, 94, 231, 214, 95, 124, 62, 226, 239, 169, 214, 9, 2, 211, 238, 155, 172, 134, 167, 45, 254, 250, 118, 147, 110, 154, 106, 2, 17, 0, 0, 0, 4, 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