Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2bcd2e413faafba2df989798db2337ee0a433bc3e8c078843a3898e805e6b9

Tx prefix hash: 60d0c71928ef67a544d86e21da28e3d2b9c4d9e80fd6a911cb22ad1f36ce835a
Tx public key: 8fa68843f04c9299352411ac1ad9b38f14720c4a009f09c0e114b7e8e0daffbf
Timestamp: 1652612223 Timestamp [UTC]: 2022-05-15 10:57:03 Age [y:d:h:m:s]: 04:183:09:31:21
Block: 501473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1176165 RingCT/type: yes/0
Extra: 018fa68843f04c9299352411ac1ad9b38f14720c4a009f09c0e114b7e8e0daffbf021100000011a8c141c5000000000000000000

1 output(s) for total of 0.013378640473 xmr

stealth address amount amount idx tag
00: dfd1de863d95c945ed3074b775ba8f8ec5e7b2bd50274e64a6cd0e04c785b604 0.013378640473 926144 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": 501483, "vin": [ { "gen": { "height": 501473 } } ], "vout": [ { "amount": 13378640473, "target": { "key": "dfd1de863d95c945ed3074b775ba8f8ec5e7b2bd50274e64a6cd0e04c785b604" } } ], "extra": [ 1, 143, 166, 136, 67, 240, 76, 146, 153, 53, 36, 17, 172, 26, 217, 179, 143, 20, 114, 12, 74, 0, 159, 9, 192, 225, 20, 183, 232, 224, 218, 255, 191, 2, 17, 0, 0, 0, 17, 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: