Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa51c12c05fb49604fd12783af2c29d03ea4eb742cb03ab17f397193aa03f19d

Tx prefix hash: 871638006da870a80061b94f9aa79d1f2ca102e1a0c37ffed77eb2aaed0660af
Tx public key: e76fc6f4f7282f406d3e48ec517808662265a032acf68f521bad042bf14854e0
Timestamp: 1653694974 Timestamp [UTC]: 2022-05-27 23:42:54 Age [y:d:h:m:s]: 04:178:22:58:35
Block: 510338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1173156 RingCT/type: yes/0
Extra: 01e76fc6f4f7282f406d3e48ec517808662265a032acf68f521bad042bf14854e0021100000012a8c141c5000000000000000000

1 output(s) for total of 0.012503699996 xmr

stealth address amount amount idx tag
00: bc88dbb624f59561d1774937a161b28a134f2e40bdd6d578587c7acc9a257cd4 0.012503699996 936645 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": 510348, "vin": [ { "gen": { "height": 510338 } } ], "vout": [ { "amount": 12503699996, "target": { "key": "bc88dbb624f59561d1774937a161b28a134f2e40bdd6d578587c7acc9a257cd4" } } ], "extra": [ 1, 231, 111, 198, 244, 247, 40, 47, 64, 109, 62, 72, 236, 81, 120, 8, 102, 34, 101, 160, 50, 172, 246, 143, 82, 27, 173, 4, 43, 241, 72, 84, 224, 2, 17, 0, 0, 0, 18, 168, 193, 65, 197, 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) | monero version: