Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ece36e85ab4b3bc3993e2ba4aa8355200cbc4c0f3edc365a44fdc6957c9328cf

Tx prefix hash: 081cc3f427235de0bf38eb6e5efeee75754343ddbfa8f1a69fd84e582353fe0b
Tx public key: 09aa6a0d377371faf7edcc6d3da7198ec844ad212c56c3e5768d005274b2474f
Timestamp: 1722565074 Timestamp [UCT]: 2024-08-02 02:17:54 Age [y:d:h:m:s]: 00:114:17:10:05
Block: 1078817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82082 RingCT/type: yes/0
Extra: 0109aa6a0d377371faf7edcc6d3da7198ec844ad212c56c3e5768d005274b2474f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3418f20bbb46e4ffcc649b9470e325b7803acc58ba49c949930d43cbf91ac6f 0.600000000000 1551512 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": 1078827, "vin": [ { "gen": { "height": 1078817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3418f20bbb46e4ffcc649b9470e325b7803acc58ba49c949930d43cbf91ac6f" } } ], "extra": [ 1, 9, 170, 106, 13, 55, 115, 113, 250, 247, 237, 204, 109, 61, 167, 25, 142, 200, 68, 173, 33, 44, 86, 195, 229, 118, 141, 0, 82, 116, 178, 71, 79, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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