Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d46720dfeb68cb52b01a57e4dfa3b0dc18f86a0ac2d8a2d935c81d4f9a8bf556

Tx prefix hash: 24c1d59b8efcb303a71b7bc7943f73e5e9a5b9a15e321dcfcf2baa8075969d4a
Tx public key: a5230044321b84c3ec7ecf482506a18aff093f605cc20cc2f6810a9705a17129
Timestamp: 1580266867 Timestamp [UTC]: 2020-01-29 03:01:07 Age [y:d:h:m:s]: 06:022:05:17:23
Block: 54624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1425421 RingCT/type: yes/0
Extra: 01a5230044321b84c3ec7ecf482506a18aff093f605cc20cc2f6810a9705a17129021100000040bd0f9f9f000000000000000000

1 output(s) for total of 0.404584125659 xmr

stealth address amount amount idx tag
00: 7ccfb1965ea4e5f3902597845ff638a6209f8e57401a538b198bba1f0db7e65e 0.404584125659 101068 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": 54634, "vin": [ { "gen": { "height": 54624 } } ], "vout": [ { "amount": 404584125659, "target": { "key": "7ccfb1965ea4e5f3902597845ff638a6209f8e57401a538b198bba1f0db7e65e" } } ], "extra": [ 1, 165, 35, 0, 68, 50, 27, 132, 195, 236, 126, 207, 72, 37, 6, 161, 138, 255, 9, 63, 96, 92, 194, 12, 194, 246, 129, 10, 151, 5, 161, 113, 41, 2, 17, 0, 0, 0, 64, 189, 15, 159, 159, 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