Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a93fe1c07f93b0ce6ae45146e5c657db8a0960f1436bfd54c5a164f9751afabe

Tx prefix hash: 71a1497a458069d8dbba690b5c4830ddb778d1d0d862a1f5c6a2e4592ab8b6a0
Tx public key: c3e54c0519170698473ceb611d4e8dcab1e94f787b3f121a4ff3ffa055dc2a1e
Timestamp: 1590429949 Timestamp [UTC]: 2020-05-25 18:05:49 Age [y:d:h:m:s]: 06:180:07:45:03
Block: 103020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1580065 RingCT/type: yes/0
Extra: 01c3e54c0519170698473ceb611d4e8dcab1e94f787b3f121a4ff3ffa055dc2a1e021100000404d2466498000000000000000000

1 output(s) for total of 0.279674411329 xmr

stealth address amount amount idx tag
00: 9954ee9b6e02b3da833b996029918d00c5a14e61e6c82ccdb4303f418c14cc31 0.279674411329 180867 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": 103030, "vin": [ { "gen": { "height": 103020 } } ], "vout": [ { "amount": 279674411329, "target": { "key": "9954ee9b6e02b3da833b996029918d00c5a14e61e6c82ccdb4303f418c14cc31" } } ], "extra": [ 1, 195, 229, 76, 5, 25, 23, 6, 152, 71, 60, 235, 97, 29, 78, 141, 202, 177, 233, 79, 120, 123, 63, 18, 26, 79, 243, 255, 160, 85, 220, 42, 30, 2, 17, 0, 0, 4, 4, 210, 70, 100, 152, 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: