Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c141199b2fcd90e6ef72a7569f977c3d05d2f40b99fda8716f8df638804b350

Tx prefix hash: 3fed9ff1a31fa2b2752ec20625f1449403f4195c101e95cc341a6977f1952ec1
Tx public key: c528d77e01b7bf9dc428bd0f63ef022dff9a1410bc5aba52cc6300e5e257fea6
Timestamp: 1647707649 Timestamp [UTC]: 2022-03-19 16:34:09 Age [y:d:h:m:s]: 04:245:23:22:14
Block: 461927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1220067 RingCT/type: yes/0
Extra: 01c528d77e01b7bf9dc428bd0f63ef022dff9a1410bc5aba52cc6300e5e257fea602110000000b4da16a3a000000000000000000

1 output(s) for total of 0.018090461111 xmr

stealth address amount amount idx tag
00: dfa29ec4c7d34c1a9e85dc0f8c9d7e59f0f8ff8e57b5c78b563c8028a88c1dd0 0.018090461111 879270 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": 461937, "vin": [ { "gen": { "height": 461927 } } ], "vout": [ { "amount": 18090461111, "target": { "key": "dfa29ec4c7d34c1a9e85dc0f8c9d7e59f0f8ff8e57b5c78b563c8028a88c1dd0" } } ], "extra": [ 1, 197, 40, 215, 126, 1, 183, 191, 157, 196, 40, 189, 15, 99, 239, 2, 45, 255, 154, 20, 16, 188, 90, 186, 82, 204, 99, 0, 229, 226, 87, 254, 166, 2, 17, 0, 0, 0, 11, 77, 161, 106, 58, 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: