Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a4fea77f79e12dc20006563e05da71389e9402f8d41dc363f0e2ff259a9165a

Tx prefix hash: 2abb9ddcecf97e2e1fd9b2ca4f78498b22df0d6f506c04acec288d51bf6063c0
Tx public key: 04f55d49a66717081bbd1b224fe58fb5d1e2e7504f5c04b6d974421a116e1873
Timestamp: 1580006664 Timestamp [UTC]: 2020-01-26 02:44:24 Age [y:d:h:m:s]: 06:024:04:14:29
Block: 52815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1426778 RingCT/type: yes/0
Extra: 0104f55d49a66717081bbd1b224fe58fb5d1e2e7504f5c04b6d974421a116e1873021100000001391a8d0e000000000000000000

1 output(s) for total of 0.410213826471 xmr

stealth address amount amount idx tag
00: 394d9bc93587c183ee9fa61255ae6de30e7db04ef8dc4fa5af104472458795e2 0.410213826471 98012 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 dinastycoin-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": 52825, "vin": [ { "gen": { "height": 52815 } } ], "vout": [ { "amount": 410213826471, "target": { "key": "394d9bc93587c183ee9fa61255ae6de30e7db04ef8dc4fa5af104472458795e2" } } ], "extra": [ 1, 4, 245, 93, 73, 166, 103, 23, 8, 27, 189, 27, 34, 79, 229, 143, 181, 209, 226, 231, 80, 79, 92, 4, 182, 217, 116, 66, 26, 17, 110, 24, 115, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369