Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf10e8791aed0b2108ef2b298bffbcb83e031849fc5064205a67d2c0040f6372

Tx prefix hash: db2249f7c39afe6c1d7637d6b7f30e1927de898d9263b299d7c83dc4acba3f99
Tx public key: 391713e69843d31482f579eac839591a4f038d8c631b958df2f50157c9a6e672
Timestamp: 1720256770 Timestamp [UCT]: 2024-07-06 09:06:10 Age [y:d:h:m:s]: 00:271:11:23:24
Block: 1059677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193963 RingCT/type: yes/0
Extra: 01391713e69843d31482f579eac839591a4f038d8c631b958df2f50157c9a6e67202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1008d788637da557945f9cdb87ae504ff6aa046867273e073da4dc64b8574965 0.600000000000 1530148 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": 1059687, "vin": [ { "gen": { "height": 1059677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1008d788637da557945f9cdb87ae504ff6aa046867273e073da4dc64b8574965" } } ], "extra": [ 1, 57, 23, 19, 230, 152, 67, 211, 20, 130, 245, 121, 234, 200, 57, 89, 26, 79, 3, 141, 140, 99, 27, 149, 141, 242, 245, 1, 87, 201, 166, 230, 114, 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