Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdca2b881ba7898a50ddd326add8df5f6d30497bd9a22a520a12e3d69a06d31

Tx prefix hash: 7681603a785a60fc796bb79c570fdf60949c52068562881a3deeb1143b020b8b
Tx public key: 904410a8d2c5252ee9c379452e4b0933cdadbe8ef3c75dbf4a19821e0a2140ad
Timestamp: 1705193719 Timestamp [UCT]: 2024-01-14 00:55:19 Age [y:d:h:m:s]: 01:304:13:52:15
Block: 934783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476511 RingCT/type: yes/0
Extra: 01904410a8d2c5252ee9c379452e4b0933cdadbe8ef3c75dbf4a19821e0a2140ad0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d96ebcf894e2e282415e45a088afb96298b6d678364021ad2f69ffd38d9776a 0.600000000000 1392799 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": 934793, "vin": [ { "gen": { "height": 934783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d96ebcf894e2e282415e45a088afb96298b6d678364021ad2f69ffd38d9776a" } } ], "extra": [ 1, 144, 68, 16, 168, 210, 197, 37, 46, 233, 195, 121, 69, 46, 75, 9, 51, 205, 173, 190, 142, 243, 199, 93, 191, 74, 25, 130, 30, 10, 33, 64, 173, 2, 17, 0, 0, 0, 9, 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