Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7986fd57bbb9443e1b7ddb275f73ad55eef3536975a3f7d768573732b4ccabb

Tx prefix hash: f5e9f93a4d758ce280fa181d3ef8d87274fd35eaf80ab8c0574dfe0e089f45ad
Tx public key: 49f0f4b50a2f67b5edde92792512b3776ef904584edff1a24323395b0d0720e8
Timestamp: 1716116021 Timestamp [UTC]: 2024-05-19 10:53:41 Age [y:d:h:m:s]: 02:184:03:54:55
Block: 1025368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656587 RingCT/type: yes/0
Extra: 0149f0f4b50a2f67b5edde92792512b3776ef904584edff1a24323395b0d0720e80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 040baa9add6dfea3cdb60aedc03f847b7c7bfa81a595cb9242c586b0aef91ed9 0.000600000000 1491817 of 15 -

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": 1025378, "vin": [ { "gen": { "height": 1025368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "040baa9add6dfea3cdb60aedc03f847b7c7bfa81a595cb9242c586b0aef91ed9" } } ], "extra": [ 1, 73, 240, 244, 181, 10, 47, 103, 181, 237, 222, 146, 121, 37, 18, 179, 119, 110, 249, 4, 88, 78, 223, 241, 162, 67, 35, 57, 91, 13, 7, 32, 232, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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: