Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e466e40ab8e30bb4dfac365966bab6cb302adf2cf4445a1a96df214d57f030

Tx prefix hash: df0f10a07f68ac7f9631f5853f371f8dd372115f10e29e10c5db13a54c0511d9
Tx public key: 9b3c6bb8f805d73860b0e1463e5eb85a080337beb717ec29aa48292944e4e66d
Timestamp: 1717615200 Timestamp [UCT]: 2024-06-05 19:20:00 Age [y:d:h:m:s]: 00:345:15:13:06
Block: 1037781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247052 RingCT/type: yes/0
Extra: 019b3c6bb8f805d73860b0e1463e5eb85a080337beb717ec29aa48292944e4e66d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb576adb94e85b33b45a223aa1e1eeffebb69fa8662031b1143707e97c5ec88e 0.600000000000 1506338 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": 1037791, "vin": [ { "gen": { "height": 1037781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb576adb94e85b33b45a223aa1e1eeffebb69fa8662031b1143707e97c5ec88e" } } ], "extra": [ 1, 155, 60, 107, 184, 248, 5, 215, 56, 96, 176, 225, 70, 62, 94, 184, 90, 8, 3, 55, 190, 183, 23, 236, 41, 170, 72, 41, 41, 68, 228, 230, 109, 2, 17, 0, 0, 0, 3, 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