Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f8328fb553974520cd708c6eb90e3c4714b0aa156dcc6457c7988b67a3c82b0

Tx prefix hash: f1e04ec7b5f907123c2281d03016a4c41ad204a7b6924308a6f96aa7e00c7240
Tx public key: ed7029efb7e921939a188066740f7efa20beb8df848db3b982cbb4aa3384cc14
Timestamp: 1723294685 Timestamp [UCT]: 2024-08-10 12:58:05 Age [y:d:h:m:s]: 00:285:01:36:33
Block: 1084878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203655 RingCT/type: yes/0
Extra: 01ed7029efb7e921939a188066740f7efa20beb8df848db3b982cbb4aa3384cc1402110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1fb251015085f4ff24549f0c6f7a3c109617701f45b58b9e36219bc63e7bc06 0.600000000000 1559309 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": 1084888, "vin": [ { "gen": { "height": 1084878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1fb251015085f4ff24549f0c6f7a3c109617701f45b58b9e36219bc63e7bc06" } } ], "extra": [ 1, 237, 112, 41, 239, 183, 233, 33, 147, 154, 24, 128, 102, 116, 15, 126, 250, 32, 190, 184, 223, 132, 141, 179, 185, 130, 203, 180, 170, 51, 132, 204, 20, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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