Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 530472780f59a7cfd929cc0071ad5c6e5d3b08b37501c06904ed29129c7b8050

Tx prefix hash: 5f961d68bacfae19a9e6b59af9d3a9650b11f3592ef2fbbdd908e4d16883b942
Tx public key: ab1e3de34965e4802248913a8df3c685a61f8d685a30b12e94bf7bfd9d417f78
Timestamp: 1703563799 Timestamp [UCT]: 2023-12-26 04:09:59 Age [y:d:h:m:s]: 01:140:03:18:47
Block: 921290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361303 RingCT/type: yes/0
Extra: 01ab1e3de34965e4802248913a8df3c685a61f8d685a30b12e94bf7bfd9d417f7802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 826c1053e413f64ca829fb7d2e6d8514a35d4bed7723591eeb375fcb040c1453 0.600000000000 1378976 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": 921300, "vin": [ { "gen": { "height": 921290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "826c1053e413f64ca829fb7d2e6d8514a35d4bed7723591eeb375fcb040c1453" } } ], "extra": [ 1, 171, 30, 61, 227, 73, 101, 228, 128, 34, 72, 145, 58, 141, 243, 198, 133, 166, 31, 141, 104, 90, 48, 177, 46, 148, 191, 123, 253, 157, 65, 127, 120, 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