Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec31bc9b4d8b6c6d448f2b8606f4c752f45b05839f1ab74a761f5ca427ceda4

Tx prefix hash: 913357806f4b7eb614b78a9394a4e14d9a9f6a5f93939c8162e751c27904a2e9
Tx public key: 17ebadf6cf6f051507e001d37557af114f129bb46d11ac70768d00c90a3efd2e
Timestamp: 1647503432 Timestamp [UTC]: 2022-03-17 07:50:32 Age [y:d:h:m:s]: 04:247:21:32:51
Block: 460238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1221426 RingCT/type: yes/0
Extra: 0117ebadf6cf6f051507e001d37557af114f129bb46d11ac70768d00c90a3efd2e0211000000092e6b1fd5000000000000000000

1 output(s) for total of 0.018324862132 xmr

stealth address amount amount idx tag
00: c4eb44f24d2a1db9b73cf11c5e493270e2240f86921dd4e5d816b8db969188a3 0.018324862132 877167 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": 460248, "vin": [ { "gen": { "height": 460238 } } ], "vout": [ { "amount": 18324862132, "target": { "key": "c4eb44f24d2a1db9b73cf11c5e493270e2240f86921dd4e5d816b8db969188a3" } } ], "extra": [ 1, 23, 235, 173, 246, 207, 111, 5, 21, 7, 224, 1, 211, 117, 87, 175, 17, 79, 18, 155, 180, 109, 17, 172, 112, 118, 141, 0, 201, 10, 62, 253, 46, 2, 17, 0, 0, 0, 9, 46, 107, 31, 213, 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: