Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa134801d8dd356540aab68cee63373bf8485e0eaab5e24f3c1daaff9bfa87d5

Tx prefix hash: 50713065bc0c488ec8dc4b0ea05feb18950fb2af1b3e1282f86f54323e7ca8b6
Tx public key: a5f885c5518999d13bb4413823370e0e53b0001d55651657c572b6d3694c8e8c
Timestamp: 1574099567 Timestamp [UTC]: 2019-11-18 17:52:47 Age [y:d:h:m:s]: 06:104:21:10:50
Block: 11966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1476456 RingCT/type: yes/0
Extra: 01a5f885c5518999d13bb4413823370e0e53b0001d55651657c572b6d3694c8e8c02110000000166a80d00000000000000000000

1 output(s) for total of 0.560212201104 xmr

stealth address amount amount idx tag
00: 79afbaba81cd8c011ddc238be876f9c5493c07db28c8d5107aacb1beb83c9b50 0.560212201104 13051 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": 11976, "vin": [ { "gen": { "height": 11966 } } ], "vout": [ { "amount": 560212201104, "target": { "key": "79afbaba81cd8c011ddc238be876f9c5493c07db28c8d5107aacb1beb83c9b50" } } ], "extra": [ 1, 165, 248, 133, 197, 81, 137, 153, 209, 59, 180, 65, 56, 35, 55, 14, 14, 83, 176, 0, 29, 85, 101, 22, 87, 197, 114, 182, 211, 105, 76, 142, 140, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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