Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b3cdb2f5b6a3476103461ec38209c6b593ec970f260c8eb18f0ebb849267248

Tx prefix hash: 12bebc745ea8e557a1eb9e102217f192960db3161ba2f64c8b768442e5234eef
Tx public key: a8cbe98a4fa88b1a2c41aca945fa88148b17eb81c88e1aa2b63e226c97f4152f
Timestamp: 1713117790 Timestamp [UCT]: 2024-04-14 18:03:10 Age [y:d:h:m:s]: 00:339:22:09:32
Block: 1000478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243052 RingCT/type: yes/0
Extra: 01a8cbe98a4fa88b1a2c41aca945fa88148b17eb81c88e1aa2b63e226c97f4152f02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9ae743a4b4513481ccbc5a8298b5acf62ccc38c158193eb36acd1c62e94f3b5 0.600000000000 1460976 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": 1000488, "vin": [ { "gen": { "height": 1000478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9ae743a4b4513481ccbc5a8298b5acf62ccc38c158193eb36acd1c62e94f3b5" } } ], "extra": [ 1, 168, 203, 233, 138, 79, 168, 139, 26, 44, 65, 172, 169, 69, 250, 136, 20, 139, 23, 235, 129, 200, 142, 26, 162, 182, 62, 34, 108, 151, 244, 21, 47, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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