Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c137acf62ce4b44a1b0c8973e86a4745e54acae613d0ae72accd29f803a5af

Tx prefix hash: f90a9253a084171f116c569cf5d99ea05ece9d33696758936575c35413d57884
Tx public key: a8c4c065d07c73213daa8a1d36c829c3009c77e2ca5688e36fe802619de1a709
Timestamp: 1636088910 Timestamp [UCT]: 2021-11-05 05:08:30 Age [y:d:h:m:s]: 03:015:22:10:04
Block: 367664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 789880 RingCT/type: yes/0
Extra: 01a8c4c065d07c73213daa8a1d36c829c3009c77e2ca5688e36fe802619de1a70902110000000d6e80e2c6000000000000000000

1 output(s) for total of 37.134445313000 dcy

stealth address amount amount idx
00: 3fde8c24c12803bdeaeff9b9fb523a1e516cb2b3c30cdc018998703edfd3efd2 37.134445313000 745968 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": 367674, "vin": [ { "gen": { "height": 367664 } } ], "vout": [ { "amount": 37134445313, "target": { "key": "3fde8c24c12803bdeaeff9b9fb523a1e516cb2b3c30cdc018998703edfd3efd2" } } ], "extra": [ 1, 168, 196, 192, 101, 208, 124, 115, 33, 61, 170, 138, 29, 54, 200, 41, 195, 0, 156, 119, 226, 202, 86, 136, 227, 111, 232, 2, 97, 157, 225, 167, 9, 2, 17, 0, 0, 0, 13, 110, 128, 226, 198, 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