Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbf80c81e3337a23b56854ab6cff4b30bd278ca8f2bca828d043249350ea8362

Tx prefix hash: 261b5ac77c7ba013f110fc87421a7c5cf9bc38e786009ebc479ccd05f27b936d
Tx public key: 3d75ddfbae1d9ec6a911f77b3f7066187b6774793eec903165c6e48f269c9070
Timestamp: 1634544668 Timestamp [UTC]: 2021-10-18 08:11:08 Age [y:d:h:m:s]: 05:033:21:21:15
Block: 355459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1326972 RingCT/type: yes/0
Extra: 013d75ddfbae1d9ec6a911f77b3f7066187b6774793eec903165c6e48f269c907002110000000bf29d7abf000000000000000000

1 output(s) for total of 0.040758405951 xmr

stealth address amount amount idx tag
00: c72dc53e9e734f1c44a2292fa1ab309e19da99979af756f6fb7f275c4ace028b 0.040758405951 725675 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": 355469, "vin": [ { "gen": { "height": 355459 } } ], "vout": [ { "amount": 40758405951, "target": { "key": "c72dc53e9e734f1c44a2292fa1ab309e19da99979af756f6fb7f275c4ace028b" } } ], "extra": [ 1, 61, 117, 221, 251, 174, 29, 158, 198, 169, 17, 247, 123, 63, 112, 102, 24, 123, 103, 116, 121, 62, 236, 144, 49, 101, 198, 228, 143, 38, 156, 144, 112, 2, 17, 0, 0, 0, 11, 242, 157, 122, 191, 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: