Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b1e7b94a4b732364f6e607b3efd8f61231c6ef4cd9732bde61723dbb3aa76b

Tx prefix hash: c1610ddd620c87650a4d434d70c138c84bfffdaddeaa220759874b7bf1362fc4
Tx public key: 09ff65acec5ceb66cef7a31fdece5b2597b796f86dad2a4995ba6d699bc025cd
Timestamp: 1708128995 Timestamp [UCT]: 2024-02-17 00:16:35 Age [y:d:h:m:s]: 01:038:11:51:08
Block: 959135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288529 RingCT/type: yes/0
Extra: 0109ff65acec5ceb66cef7a31fdece5b2597b796f86dad2a4995ba6d699bc025cd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfd79efb00292bdff0103348b813c8cbfcbd22b19a76b8d8384a960b4e341dba 0.600000000000 1418666 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": 959145, "vin": [ { "gen": { "height": 959135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfd79efb00292bdff0103348b813c8cbfcbd22b19a76b8d8384a960b4e341dba" } } ], "extra": [ 1, 9, 255, 101, 172, 236, 92, 235, 102, 206, 247, 163, 31, 222, 206, 91, 37, 151, 183, 150, 248, 109, 173, 42, 73, 149, 186, 109, 105, 155, 192, 37, 205, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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