Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbefb3ee0f4d714e13d5f4671b49acf500c6f64b5d342160fb5eb32b506d8050

Tx prefix hash: ce4cc5ce1e2b0c41c3f5fc3679ff12a6805e8236a3bda84843c552c0b1af4672
Tx public key: d9c0a22625728e5567811decf97a99e0cdbfaaeb432d8e993a37de562a5ea7e8
Timestamp: 1675250193 Timestamp [UCT]: 2023-02-01 11:16:33 Age [y:d:h:m:s]: 02:132:02:25:40
Block: 687436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 616036 RingCT/type: yes/0
Extra: 01d9c0a22625728e5567811decf97a99e0cdbfaaeb432d8e993a37de562a5ea7e8021100000004e7ace25d000000000000000000

1 output(s) for total of 3.237718564000 dcy

stealth address amount amount idx
00: 260d3c5ed4fa1f52d5f8bd6d10aeff178a8cefa159ea1d0860fc8c5901946221 3.237718564000 1129998 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": 687446, "vin": [ { "gen": { "height": 687436 } } ], "vout": [ { "amount": 3237718564, "target": { "key": "260d3c5ed4fa1f52d5f8bd6d10aeff178a8cefa159ea1d0860fc8c5901946221" } } ], "extra": [ 1, 217, 192, 162, 38, 37, 114, 142, 85, 103, 129, 29, 236, 249, 122, 153, 224, 205, 191, 170, 235, 67, 45, 142, 153, 58, 55, 222, 86, 42, 94, 167, 232, 2, 17, 0, 0, 0, 4, 231, 172, 226, 93, 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