Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d16554bb570299d77a6b28727b1d1a95346a6fa3c2b14dfed178c6a1fd9e98

Tx prefix hash: af0a6ff26cb95d3aa7a2bb0153ae32fca13a356555ad8375115c8686d53bdfe5
Tx public key: 79ffb3bc66d0dbe35175e8418a1e24b79bcdb12478bab4f63b208db94c4a0ed3
Timestamp: 1702461681 Timestamp [UCT]: 2023-12-13 10:01:21 Age [y:d:h:m:s]: 01:126:16:21:01
Block: 912173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351659 RingCT/type: yes/0
Extra: 0179ffb3bc66d0dbe35175e8418a1e24b79bcdb12478bab4f63b208db94c4a0ed3021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600050000000 dcy

stealth address amount amount idx
00: 48e197c8ccd61103a18984684ee16aac05e4eb414bbddf690d071ea91e13162b 0.600050000000 1369393 of 0

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": 912183, "vin": [ { "gen": { "height": 912173 } } ], "vout": [ { "amount": 600050000, "target": { "key": "48e197c8ccd61103a18984684ee16aac05e4eb414bbddf690d071ea91e13162b" } } ], "extra": [ 1, 121, 255, 179, 188, 102, 208, 219, 227, 81, 117, 232, 65, 138, 30, 36, 183, 155, 205, 177, 36, 120, 186, 180, 246, 59, 32, 141, 185, 76, 74, 14, 211, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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