Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbecd843f4409265d642482a6a3e125f2257b7e87a29b338e12befc0d5872079

Tx prefix hash: 8c1b2123c117050fd635c0ea5be8d1185ccf7c2f030b382e8b75af8f7f505979
Tx public key: ba652e496a81131210e2b033e8ef87bf7debc5af16c703b2820bcd640116b7ce
Timestamp: 1699872049 Timestamp [UCT]: 2023-11-13 10:40:49 Age [y:d:h:m:s]: 01:185:01:42:32
Block: 890690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393473 RingCT/type: yes/0
Extra: 01ba652e496a81131210e2b033e8ef87bf7debc5af16c703b2820bcd640116b7ce02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.686711443000 dcy

stealth address amount amount idx
00: d31885e0c07bfec80ade53a04c0538f1ab3a74d75d024a4b96e0f986572d261d 0.686711443000 1346719 of 0

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": 890700, "vin": [ { "gen": { "height": 890690 } } ], "vout": [ { "amount": 686711443, "target": { "key": "d31885e0c07bfec80ade53a04c0538f1ab3a74d75d024a4b96e0f986572d261d" } } ], "extra": [ 1, 186, 101, 46, 73, 106, 129, 19, 18, 16, 226, 176, 51, 232, 239, 135, 191, 125, 235, 197, 175, 22, 199, 3, 178, 130, 11, 205, 100, 1, 22, 183, 206, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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