Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f796bd08bffa73bff4354435c7d70d0ee30fbd063ff559471690162e644e4b

Tx prefix hash: 6092648c24b040b4cebcb0c47dfaaae2a05b3bd04c0edbced18aa92ec74ea18e
Tx public key: a62559e44f2b5cd99b21d73fc7b6923dcec03b6dbf21ad80dd495dd5eca6c7a2
Timestamp: 1711688484 Timestamp [UCT]: 2024-03-29 05:01:24 Age [y:d:h:m:s]: 00:273:04:01:47
Block: 988661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195523 RingCT/type: yes/0
Extra: 01a62559e44f2b5cd99b21d73fc7b6923dcec03b6dbf21ad80dd495dd5eca6c7a20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19f84d3d676bc6806a9c69b5b9046c2f84e71f45a129b45a9d24c2d63dcf971b 0.600000000000 1448942 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": 988671, "vin": [ { "gen": { "height": 988661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19f84d3d676bc6806a9c69b5b9046c2f84e71f45a129b45a9d24c2d63dcf971b" } } ], "extra": [ 1, 166, 37, 89, 228, 79, 43, 92, 217, 155, 33, 215, 63, 199, 182, 146, 61, 206, 192, 59, 109, 191, 33, 173, 128, 221, 73, 93, 213, 236, 166, 199, 162, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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