Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4a365a80cfa8b07fca3536b57377f8ea5047b61366d37f23713c1839a920200

Tx prefix hash: 07695cc53a1c51f6c0d818d66d6fd3684ee6d1e9f850470837dca17a6b87e9cb
Tx public key: 263679e34fd196229dafe895e6ece1844bd07b2ac463e4121aa960e4099d6b6b
Timestamp: 1672018402 Timestamp [UCT]: 2022-12-26 01:33:22 Age [y:d:h:m:s]: 01:325:12:07:55
Block: 660652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493622 RingCT/type: yes/0
Extra: 01263679e34fd196229dafe895e6ece1844bd07b2ac463e4121aa960e4099d6b6b02110000000975e3f0e9000000000000000000

1 output(s) for total of 3.971784213000 dcy

stealth address amount amount idx
00: 57fb560868ed6451669efe0dde35ce0636cf9cdd01f8bb2b6b737c5c1b56f6a1 3.971784213000 1101385 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": 660662, "vin": [ { "gen": { "height": 660652 } } ], "vout": [ { "amount": 3971784213, "target": { "key": "57fb560868ed6451669efe0dde35ce0636cf9cdd01f8bb2b6b737c5c1b56f6a1" } } ], "extra": [ 1, 38, 54, 121, 227, 79, 209, 150, 34, 157, 175, 232, 149, 230, 236, 225, 132, 75, 208, 123, 42, 196, 99, 228, 18, 26, 169, 96, 228, 9, 157, 107, 107, 2, 17, 0, 0, 0, 9, 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